I'm a professional PHP, Python and Javascript developer from the UK. I've worked with Django, Laravel, and React, among others. I also maintain a legacy Zend 1 application.
Because going with the grain of HTTP means things like HTTP caching are more likely to work as expected. If your site is behind a caching proxy like Varnish, then using the correct HTTP methods means it's more likely to "just work" as expected because Varnish knows what each one does and can act accordingly. You can work around this by writing your own rules, but why do that if you don't have to?
I'm a professional PHP, Python and Javascript developer from the UK. I've worked with Django, Laravel, and React, among others. I also maintain a legacy Zend 1 application.
You should also bear in mind that some users may be behind a proxy you don't control, such as if their employer uses a web proxy like Squid to reduce the bandwidth used.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Because going with the grain of HTTP means things like HTTP caching are more likely to work as expected. If your site is behind a caching proxy like Varnish, then using the correct HTTP methods means it's more likely to "just work" as expected because Varnish knows what each one does and can act accordingly. You can work around this by writing your own rules, but why do that if you don't have to?
Might be related -- blog.logrocket.com/graphql-vs-rest...
I should try varnish-cache.org/ someday, especially if I use AWS or DigitalOcean.
You should also bear in mind that some users may be behind a proxy you don't control, such as if their employer uses a web proxy like Squid to reduce the bandwidth used.