HttpOnly needs updates

[kingthorin]

I just finished dealing with auto-migrated issues for this article, it could definitely use some content updates:
https://github.com/OWASP/www-community/blob/master/pages/HttpOnly.md it still talks about old versions of IE and Opera.

This article includes an extensive table that needs re-working after the auto-migration as well (which I did not tackle).

Is Opera even relevant in 2020? Do we still care about IE with Edge/Edge Chrome?

[rangira]

After taking a look at the documentation one more suggestion. Should the examples be rewritten because now applications dont use servlets anymore. Also we are on Java 11 and .Net 3.5.
Please also share how should various browsers versions be verified to update the page. Does each browser need to be tested for HttpOnly first.

[kingthorin]

The whole thing can be re-written. The content should simply be written with modern details and cover the three or four currently relevant browsers (Chrome (Edge Chrome), Firefox, Safari, Edge).

[rangira]

I will try to create smaller PRs in chunks instead of making changes in the whole page in one in one PR.

[kingthorin]

Great!

[kingthorin]

@rangira got something ready yet?

[kingthorin]

@rangira got something ready yet?

[Prakhar-Shankar]

@kingthorin Can you please suggest me, from where should I fetch the latest data?

[kingthorin]

Well you could start by dumping content related to browsers that are gone (IE) or barely used (Opera).

The other details you might have to research or test manually.

If needed/wanted you can get Windows Development VMs here: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/

[shrutibhardwaj22]

I want to work on this issue. please assign me this issue.