-
Notifications
You must be signed in to change notification settings - Fork 664
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
Support HEAD HTTP request method #165
Comments
Alright, HEAD support will be added to motionEye :) |
Added with commit 0d78dd0. |
Hm, you have added HEAD support only for main page, but not for https://example.com/picture/1/current/ one. And that mobile app still gets 405 when asking for a HEAD. I think it will be better to add HEAD support for all pages, because HEAD is used to validate that resource exists. I don't see any cons. Should I create new issue? |
It's done: d78a9c1 :). |
Great man! Now it accepts |
Hmm that means I'd have to implement separate HEAD methods for each possible URIs. I never thought any piece of software written these days would rely on the existence (and the result) of the HEAD method. I guess I'd probably need to properly write HEAD methods for various URIs available. |
Yep, |
I think that motioneye should support HEAD method. It will allow to detect fast (related to mobile network) if motioneye is still working. E.g. this mobile app uses HEAD request to check validate image url and it fails for motioneye :(.
I can't imagine any argument against HEAD support. Even google.com supports HEAD.
The text was updated successfully, but these errors were encountered: