Re: Issue 276433 in chromium: Double Redirect (HTTP 302) issued in Chrome, not IE and Firefox on Client Browser

[chro...@googlecode.com]

Updates:
Labels: Cr-Internals-Network-HTTP

Comment #3 on issue 276433 by tk...@chromium.org: Double Redirect (HTTP
302) issued in Chrome, not IE and Firefox on Client Browser
http://code.google.com/p/chromium/issues/detail?id=276433

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #5 on issue 276433 by mightaswelby: Double Redirect (HTTP 302)

issued in Chrome, not IE and Firefox on Client Browser
http://code.google.com/p/chromium/issues/detail?id=276433

Anyone have an update on this? I have been working with one of my network
guys, and we have come to this conclusion. Can anyone verify and explain
why?

Chrome V26-28 does not cache HTTP 404 responses. If the site does not have
a favicon it asks for it on EVERY request. Secondly on a favicon request no
cookies are sent in even though they were sent on the initial connection.
Since the load balancer does not receive the session cookie from browser
it treats it as a new connection and routes the user to a server where the
user does not have a valid session resulting in an error and the user must
login again.

[chro...@googlecode.com]

Comment #6 on issue 276433 by mme...@chromium.org: Double Redirect (HTTP

302) issued in Chrome, not IE and Firefox on Client Browser
http://code.google.com/p/chromium/issues/detail?id=276433

We've gone back and forth on sending cookies with favicon requests. IE has
its own separate cookie store for them, and we've seen sites with all sorts
of fun and interesting bugs related to favicon requests, some only
triggered when they do include cookies, some only triggered when they don't
include cookies.

While I know nothing about the favicon-specific code, we aren't getting a
404 for the favicon request for the above site. We're getting 2
uncacheable redirects followed by an uncacheable login page, so it clearly
can't be stored in the HTTP cache, at least.

[chro...@googlecode.com]

Updates:
Cc: rponn...@chromium.org
Labels: Needs-Feedback

Comment #7 on issue 276433 by rponn...@chromium.org: Double Redirect (HTTP

302) issued in Chrome, not IE and Firefox on Client Browser

https://code.google.com/p/chromium/issues/detail?id=276433

Unable to repro this issue on windows using latest stable: 42.0.2311.90.

Observed error :: We could not process your request.

Could you please upgrade to latest stable: 42.0.2311.90 and re-check this
issue. If issue is still exists, pleas update the thread.

[chro...@googlecode.com]

Updates:
Status: Archived

Comment #8 on issue 276433 by b...@chromium.org: Double Redirect (HTTP 302)

issued in Chrome, not IE and Firefox on Client Browser
https://code.google.com/p/chromium/issues/detail?id=276433

Closing for lack of activity.