You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An error response of Bad Request is returned, see screenshot. At the bottom of the response, the shared services httpd server appears to be the responding server which is why I'm adding a ticket to this repo.
What did you expect?
I expected the server to either 1) ask me to login if my session/token has expired or 2) return the results of what i expect from visiting the service identified after the <project>/<venue>/ in the URL.
Reproducible steps
How would we reproduce this bug? Please walk us through it step by step. Plain-text snippets preferred but screenshots welcome.
I'm unsure of the exact steps to reproduce this behavior, but from what I've observed, if one let's some time go by after successfully logging in, and then later revisits the same URL, this response is given.
I've also observed that clearing cookies in the browser resolves this issue.
What is your environment?
Include any computer hardware, operating system, framework, browser, time-of-day or other contextual information related to your issue
Operating System: MacOSX
Browser: Firefox ESR
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked, but didn't find anything.
Describe the bug
When navigating to a URL in a venue, e.g. https://www.dev.mdps.mcp.nasa.gov:4443/unity/dev/ui
An error response of
Bad Request
is returned, see screenshot. At the bottom of the response, the shared services httpd server appears to be the responding server which is why I'm adding a ticket to this repo.What did you expect?
I expected the server to either 1) ask me to login if my session/token has expired or 2) return the results of what i expect from visiting the service identified after the
<project>/<venue>/
in the URL.Reproducible steps
I'm unsure of the exact steps to reproduce this behavior, but from what I've observed, if one let's some time go by after successfully logging in, and then later revisits the same URL, this response is given.
I've also observed that clearing cookies in the browser resolves this issue.
What is your environment?
The text was updated successfully, but these errors were encountered: