Update guide to reflect browser compatibility for HTTP verbs

[rachel-carvalho]

Summary

This updates the security guide to reflect how most browsers now do support all restful HTTP verbs.

Other Information

I was reading up on CSRF because I have an API controller that didn't pass brakeman validation for not having protect_from_forgery.

I ended up on Rails Guides for how to handle CSRF and it says this (my emphasis):

The HTTP protocol basically provides two main types of requests - GET and POST (and more, but they are not supported by most browsers)

Which I thought weird because it seemed to me that most browsers do currently support all RESTful methods. And MDN confirmed what I thought.

So I decided to update the text to say that Some legacy web browsers don't support the other methods.

I appreciate any improvements on the wording, especially because I'm not a native English speaker.

[rails-bot]

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @schneems (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

[maclover7]

👍 Thank you for your contribution!

❤️ 💚 💙 💛 💜

[rachel-carvalho]

Wow this was the fastest Pull Request resolution I've ever seen! Thank you and keep up the great job guys ❤️❤️❤️