-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Closed
Labels
B-gridEverything grid and server relatedEverything grid and server related
Description
Meta
OS: macOS
Selenium Version: 3.11, code indicates this should be in master still
Browser: Chrome
Expected Behavior
When visiting a page/servlet that does not exist in Grid, a 404 status code should be returned.
Actual Behavior
A 200 status code is returned for pages that do not exist.
Steps to reproduce
- Launch a hub or node
- Open your browser's network tab
- Visit localhost:4444/thisdoesntexist
Request URL: http://localhost:4444/thisdoesntexist
Request Method: GET
Status Code: 200 OK
More Information
It appears the design for any non-registered routes to direct to DisplayHelpServlet
, which returns the 200.
Considering I typed a page that should not exist, I feel it may be more obvious if a 404 is returned to indicate a problem.
Context: My application was requesting a custom servlet by the wrong name, and became confused when a 200 was returned but the proper action did not occur. A 404 would have very quickly jumped out as a route issue.
Metadata
Metadata
Assignees
Labels
B-gridEverything grid and server relatedEverything grid and server related