Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Validate whether url timestamping is needed for most browsers #98

Closed
plievone opened this Issue Jan 31, 2013 · 2 comments

Comments

Projects
None yet
3 participants
Contributor

plievone commented Jan 31, 2013

On my brief testing, even latest Chromium and Firefox (on Ubuntu) needed timestamping to prevent unneccessary looping due to browser caching when xhr-polling. It was visible only when debugmode was on, firebug etc showed only successful requests as usual, but there were tens and even hundreds of "shadow responses" flowing in the debug log for each socket.send.

Contributor

rauchg commented Jan 31, 2013

Also consider Cache-Control

Contributor

ruxkor commented May 2, 2013

firebug etc showed only successful requests as usual, but there were tens and even hundreds of "shadow responses" flowing in the debug log for each socket.send

we have experienced the same issue with firebug. strangely it does not occur with the ie developer tools, firebug lite or the webkit developer tools.

this was only a development/debugging issue however, and it is currently not causing any problems on chrome/safari/firefox.

@rauchg rauchg closed this May 2, 2013

@JeremyWright JeremyWright pushed a commit to goinstant/engine.io-client that referenced this issue Jun 4, 2013

@rauchg rauchg Merge pull request #98 from indutny/feature-heartbeat-on-data
socket: reset ping timeout on incoming data
1fb41d8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment