Anonymous | Login | Signup for a new account | 12-17-2024 10:38 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0004218 | [Resin] | minor | always | 09-17-10 12:44 | 11-02-10 15:48 | ||||
Reporter | stbu | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 3.1.10 | ||||||
Summary | 0004218: HTTP OPTIONS request to non-existent file or directory caused 501 (and alert in /resin-admin) | ||||||||
Description |
curl -v -X OPTIONS http://localhost:8080/ [^] => works fine, Resin respons "HTTP/1.1 200 OK". Nothing to complain about. curl -v -X OPTIONS http://localhost:8080/bogus/ [^] => In this case, Resin responds "HTTP/1.1 501 Method not implemented" Two Issues: 1.) The 501 is counted as a 500 Issue in the /resin-admin (Summary tab and WebApp tab). This is quite annoying as it pulls your attention to check the logs for any issues with the affected web-app when the last "500" did just happened a short time ago -> but you can't find it in any of your logs, but in the access.log there is for example such an entry: ... "OPTIONS /downloads HTTP/1.1" 501 162 "-" "Microsoft-WebDAV-MiniRedir/6.1.7600" 2.) Why 501 and not 404 for such a Request to a non existent file or folder? |
||||||||
Additional Information | While the above applies for Resin Professional 3.1.10, the same behaviour can be observed with Resin 4.0.9. | ||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |