mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #986] Log 404 NOT FOUND for paths that don't exist #2544
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2544
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NiceGuyIT on GitHub (Feb 23, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/986
Originally assigned to: @sadnub on GitHub.
Is your feature request related to a problem? Please describe.
The frontend (
rmm.example.com) is logging HTTP 200 for paths that don't exist.Describe the solution you'd like
I would like the server to conform to the standard HTTP codes and return a 404 if the path doesn't exist.
Here's the nginx log for the above request.
Describe alternatives you've considered
I've considered not reporting this.
Additional context
While researching a problem, I ran across logs showing HTTP 200 for
/owa/auth/logon.aspx, a URL common to Outlook Web Access. This seems to imply the server is hacked and responding to a valid request. That is not the case, though, as that path doesn't exist on the server.@wh1te909 commented on GitHub (Feb 23, 2022):
yea this by design and how SPA's work see https://router.vuejs.org/guide/essentials/history-mode.html#caveat
it is really annoying though I agree.
@silversword411 commented on GitHub (Feb 23, 2022):
Sounds like no options on this one. Closing, post if you find some workaround.
@NiceGuyIT commented on GitHub (Feb 23, 2022):
For future reference. How do I correctly deal with 404 HTTP errors when using an SPA and no server-side computation?