Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
4218 | minor | always | 09-17-10 12:44 | 11-02-10 15:48 | |
|
|||||
Reporter: | stbu | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 3.1.10 | ||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 4.0.13 | ||
|
|||||
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? |
||||
Steps To Reproduce: | |||||
Additional Information: | While the above applies for Resin Professional 3.1.10, the same behaviour can be observed with Resin 4.0.9. | ||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|