-
Notifications
You must be signed in to change notification settings - Fork 123
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.
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
satosa.exception.SATOSAUnknownError: Unknown error in the log #474
Comments
The immediate issue is that
In practice, this means that this was caused by a HEAD request. Either the proxy should check and drop HEAD requests, or you handle this from the Web Server that sits in front of the proxy (HAProxy, nginx, etc). This is not critical issue, but it is good to add a handler to avoid these exceptions. We need to agree on the behaviour/response and ensure that the response will not affect the follow-up "normal" request. |
The example above was perhaps the best, and perhaps incomplete. Some more logs (but these doesn't seem to cause a exception at least)
etc. etc. You're probably right, make the handler deal with HEAD request to stop the exceptions filling the log would be a good thing 👍 |
(btw. some (poor-mans) loadbalancers uses HEAD requests to check that a web-service is up and running) |
I've also seen HEAD requests causing issues with other applications - triggered by Safe Browsing feature in Microsoft (web) Outlook. When clicking on a link in an email, Microsoft first sends a HEAD to the URL to "check it" before actually opening the link in your browser. Not sure if this is what caused the HEAD requests here .... |
Yes, this is usually part of a "prefetching" strategy of apps or browsers. They open a connection using the HEAD request so that if users click the link the transition is faster. |
any updates ? |
Code Version
v8.4.0
Expected Behavior
Try to catch this error to avoid all the tracebacks in log, please
Current Behavior
Lots of Tracebacks like this in the logs:
Possible Solution
Steps to Reproduce
The text was updated successfully, but these errors were encountered: