New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wrong 200 OK status #16

Open

vrbanecd opened this issue Jan 11, 2024 · 1 comment

Collaborator

vrbanecd commented Jan 11, 2024

Gave a 200 OK status when it was actually not working.

Collaborator

paulmillar commented Jan 11, 2024

Thanks for reporting this, but could you maybe add some more details?

What are the symptoms you're seeing; for example, how do you know it wasn't working (perhaps log entries)?

Were you able to localise this "not working" to either StoRM or the python proxy?

Were you able to reproduce the problem? If so, what are the steps does one need to do in order to demonstrate the problem?

When reproducing the problem, how often do you see the issue (all the time, roughly 50%, 10%, ...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment