Describe the bug
The swagger page returns status code 404 on refresh, but still loads contents. This breaks reverse proxies.
Expected behavior
Page status code should not be 404
To Reproduce
Steps to reproduce the behavior:
- Navigate to a CDA instance that's using vite/react, such as https://cwms-data.usace.army.mil/cwms-data
- Open Developer console, go to Network tab
- Click on API Docs -> Swagger UI
- Notice page loads fine (aside from possible CORS issues.
- Refresh the page (F5)
- Notice the /swagger-ui page in the network tab reports 404
- Page contents load normally.
Note: It also happens if you directly paste the swagger URL (https://cwms-data.usace.army.mil/cwms-data/swagger-ui) into the address bar, but it's more difficult to see due to needing the developer console.
CDA Version (please complete the following information):
At the top of any instance of CDA you will see a version. Please provide that version.
Additional context
When CDA is behind a reverse proxy, the proxy detects the 404 and returns a standard error page, instead of the supplied contents. So it just says "Document not found."

Describe the bug
The swagger page returns status code 404 on refresh, but still loads contents. This breaks reverse proxies.
Expected behavior
Page status code should not be 404
To Reproduce
Steps to reproduce the behavior:
Note: It also happens if you directly paste the swagger URL (https://cwms-data.usace.army.mil/cwms-data/swagger-ui) into the address bar, but it's more difficult to see due to needing the developer console.
CDA Version (please complete the following information):
At the top of any instance of CDA you will see a version. Please provide that version.
Additional context
When CDA is behind a reverse proxy, the proxy detects the 404 and returns a standard error page, instead of the supplied contents. So it just says "Document not found."