Sign in to follow this  

[web] the status of Web Sockets

This topic is 2539 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

The issue is with how some proxy servers handle HTTP header data. With the new scheme, it's theoretically possible to poison the proxy cache for all users, using the WebSocket interface.

See here for more information.

I'm looking forward to when it's resolved; JS needs WebSockets (and needs fundamental WS security flaws like it needs a hole in the head).

Share this post


Link to post
Share on other sites

This topic is 2539 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this