Discussion:
Issue 131775 in chromium: ERROR The requested URL could not be retrieved The request or reply is too large.
(too old to reply)
c***@googlecode.com
2012-06-08 10:20:05 UTC
Permalink
Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined OS-Windows

New issue 131775 by ***@gmail.com: ERROR The requested URL could not
be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Chrome Version : 19.0.1084.52
OS Version: 5.1 (Windows XP)
URLs (if applicable) : All
Other browsers tested: IE 8.0.6001.18702, Firefox 11.0, and Opera 11.64.
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: n/a
Firefox 4.x: 11.0 OK
IE 7/8/9: 8 OK
Opera 11.64 OK

What steps will reproduce the problem?
1. Do a Google search on anything (I chose: Anthony Laforge Google Chrome)
on Chrome 19.0.1084.52,
2. Right click cache link on any search result and open in new tab/window
3. Outcome:

"ERROR

The requested URL could not be retrieved

While trying to retrieve the URL:
http://webcache.googleusercontent.com/search?

The following error was encountered:

The request or reply is too large.
If you are making a POST or PUT request, then your request body (the thing
you are trying to upload) is too large. If you are making a GET request,
then the reply body (what you are trying to download) is too large. These
limits have been established by the Internet Service Provider who operates
this cache. Please contact them directly if you feel this is an error.

Your cache administrator is webmaster."

What is the expected result? No "ERROR" message and cache of search opens
with search terms in color...

This is Google's cache of
http://googlechromereleases.blogspot.com/2011/09/stable-channel-update_16.html.
It is a snapshot of the page as it appeared on 24 May 2012 08:58:01 GMT.
The current page could have changed in the meantime. Learn more

Text-only versionThese search terms are highlighted: anthony laforge google
chrome


What happens instead?

"ERROR

The requested URL could not be retrieved

While trying to retrieve the URL:
http://webcache.googleusercontent.com/search?

The following error was encountered:

The request or reply is too large.
If you are making a POST or PUT request, then your request body (the thing
you are trying to upload) is too large. If you are making a GET request,
then the reply body (what you are trying to download) is too large. These
limits have been established by the Internet Service Provider who operates
this cache. Please contact them directly if you feel this is an error.

Your cache administrator is webmaster."


Please provide any additional information below. Attach a screenshot if
possible. For screenshot refer to issues #81511 and #81772. I had attached
it back in May 2011. Same symptom.

UserAgentString: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.5 (KHTML,
like Gecko) Chrome/19.0.1084.52 Safari/536.5



Attachments:
Error.JPG 105 KB
Firefox.JPG 139 KB
IE8.JPG 152 KB
Opera.JPG 138 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-08 23:49:06 UTC
Permalink
Updates:
Cc: ***@chromium.org ***@chromium.org

Comment #1 on issue 131775 by ***@google.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

To double check, are you using a proxy, like squid proxy? Based on
http://code.google.com/p/chromium/issues/detail?id=81511 it sounds like the
issue might be related to a problem in the proxy/caching layer (i.e. for
some strange reason it's returning content that's too big for Chrome to
digest).

The suggested regression range is between 1084.46 and 1084.52, which did
include some net/proxy related changes
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/branches/1084/src&range=138391:135956&mode=html.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-08 23:51:06 UTC
Permalink
Updates:
Cc: ***@chromium.org ***@chromium.org

Comment #2 on issue 131775 by ***@google.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Adding Jim and Chris too.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-09 00:48:07 UTC
Permalink
Comment #3 on issue 131775 by ***@chromium.org: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Also note, as per discussion with laforge, perchance the newest stable push
of said proxy was done on June 8th, 2012, which *might* be a regression
point in said proxy.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-09 01:37:07 UTC
Permalink
Comment #4 on issue 131775 by ***@chromium.org: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

The URL being loaded in Chrome is different than those from the other
browsers.

The screenshots show IE/Firefox/Opera loading what I presume was this URL:

http://webcache.googleusercontent.com/search?q=cache:Pngf81Wd4YsJ:googlechromereleases.blogspot.com/2011/09/stable-channel-update_16.html+&cd=1&hl=en&ct=clnk&gl=us

Whereas the screenshot for Chrome clearly shows a different URL in the
omnibar. I can't see the whole thing, but the start of query: looks
like "q=cache:16gf72" which is definitely different from "q=cache:Pngf81".

Either that was a mistake with your experiment (clicking different links),
or that is the cause of this problem. I notice from the screenshot that you
have some Chrome extensions installed, they could possibly be re-writing
URLs.

(1) Try disabling all of your Chrome extensions by going to
chrome://chrome/extensions/.

(2) Try loading the URL I pasted above directly this time.

(3) Check to see what proxy settings you are using in Chrome by visiting
chrome://net-internals/#proxy. If you are using different proxy settings
from other browsers, try changing that.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-09 09:36:05 UTC
Permalink
Comment #5 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Mr. Laforge et al.,

I now have Chrome channel "19.0.1084.56 m" installed, but same "ERROR"
problem persists. I have (1) disabled all extensions, (2) reloaded the URL
you pasted (same "ERROR" problem), and (3) I'm not quite sure how to do
this. Nonetheless, someone mentioned "Squid" proxy. I searched to see what
proxy my office is using and found that it's "squid/2.5.STABLE1". But, not
all Chrome channels (my case for reverting back to channel 19.0.1084.46)
are affected by this proxy! So, somewhere along the line from channel
19.0.1084.46 to 19.0.1084.52->54->56 someone has made a mistake somewhere.
In order to lay to rest any doubts about the start of query ("looks
like "q=cache:16gf72" which is definitely different from "q=cache:Pngf81"),
I'll repeat the screenshots (I've since updated Firefox from v.11 to v.13)
and attach them below.

Attachments:
Chrome.bmp 2.3 MB
Firefox.bmp 2.3 MB
IE8.bmp 2.3 MB
Opera.bmp 2.3 MB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-09 09:47:57 UTC
Permalink
Comment #6 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Mr. Laforge,

I now have Chrome channel "19.0.1084.56 m" installed, but same "ERROR"
problem persists. I have (1) disabled all extensions, (2)
reloaded the URL you pasted (same "ERROR" problem), and (3)
I'm not quite sure how to do this. Nonetheless, someone
mentioned "Squid" proxy. I searched to see what proxy my office is
using and found that it's "squid/2.5.STABLE1". But, not all Chrome
channels (my case for reverting back to channel 19.0.1084.46) are
affected by this proxy! So, somewhere along the line from channel
19.0.1084.46 to 19.0.1084.52->54->56 someone has made a mistake
somewhere. In order to lay to rest any doubts about the start
of query ("looks like "q=cache:16gf72" which is definitely
different from "q=cache:Pngf81"), I've repeated the
screenshots (I've since updated Firefox from v.11 to v.13) and filed
them as a bug (Issue 131775).


Thank you so much for taking time to resolve this (most irritating) issue.


Sincerely,


***@gmail.com
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-18 05:44:39 UTC
Permalink
Comment #8 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Mr. Bentzel,
I apologize for the delayed response. I recently installed some Windows
updates (Windows-KB913086-201206) and opening Google search caches seem
to "partially" work. By "partially" I mean that previously the search terms
are color coded, which makes scanning documents very quick and convenient,
however, with the current Chrome channel (19.0.1084.56) (a) the search
terms do not appear, and (b) terms are not color coded in the cached text.
I've attached some screen shots for reference.
Thank you so much for your continued efforts to resolve this ongoing
problem.
Sincerely,
***@gmail.com

Attachments:
Chrome_ch_19.0.1084.56.JPG 145 KB
Firefox_v_13.0.JPG 140 KB
IE8.JPG 149 KB
Opera_v_11.64.JPG 137 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-18 06:08:52 UTC
Permalink
Comment #9 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Mr. Bentzel,

Attachments:
net-internals-log.json 608 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-18 06:23:04 UTC
Permalink
Comment #10 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Mr. Bentzel,
I have run into a problem following the "chrome://net-internals." I've
followed the instructions given until step 3. In
the "chrome://net-internals" tab I clicked on "Dump to file" and nothing
happens, so I just copied everything (cache & right click) in the address
bar
(http://webcache.googleusercontent.com/search?q=cache:Pngf81Wd4YsJ:googlechromereleases.blogspot.com/2011/09/stable-channel-update_16.html+&cd=1&hl=en&ct=clnk)
and pasted it. Now after clicking on the "Dump to file" button,
a "net-internals-log.json" file is produced. I'm attaching this file to
you. I hope I did it right. If not please give me more detailed steps on
how to accomplish this.
Thank you so much.
Sincerely,
***@gmail.com

Attachments:
net-internals-log.json 608 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-21 04:51:39 UTC
Permalink
Comment #13 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Messrs Bentzel & Roman,
I must apologize for the delayed response. A reason for the delay was that
during the past 2 days Chrome channel 19.0.1084.56 seemed to be responding
perfectly--meaning webcaches seemed to be fully functional, search terms
being highlighted and all. However, after logging on my terminal today any
Chrome webcache seems to be malfunctioning as reported last (no ERROR
messages but webcache search terms are not present (and so not color
coded)). I've attached a screen print herewith.
Thank you, gentlemen, for your tireless efforts in resolving this bug.
Sincerely,
***@gmail.com
P.S. I'll perform another "chrome://net-internals" after I restart Chrome
and attach the log file following transmission of this bug report.

Attachments:
Cache_062112.JPG 148 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-06-21 05:04:39 UTC
Permalink
Comment #14 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Gentlemen,
I'm pleasantly surprised! It seems Chrome is now back to functioning
perfectly: webcaches are color coded as they should be. I'm attaching both
the "chrome://net-internals" log file and the latest screen print.
Please resolve this problem. Chrome without the webcache problem is my
browser choice, but with the bug, I have no recourse but to use a
competitor's.
Thank you gentlemen, for your tireless efforts to resolve all Chrome bugs.
Sincerely,
***@gmail.com

Attachments:
net-internals-log.json 773 KB
Cache_062112_11.50_am_Thailand_Time.JPG 150 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-10-22 08:53:41 UTC
Permalink
Comment #15 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear Mr. Anthony LaForge et al.,

I apologize for having to revive this issue once again. The symptoms are
almost the same as when I first raised the subject with you back in June.
However, instead of the old error message (see enclosed in quotation marks):

"ERROR

The requested URL could not be retrieved

While trying to retrieve the URL:
http://webcache.googleusercontent.com/search?

The following error was encountered:

The request or reply is too large.
If you are making a POST or PUT request, then your request body (the thing
you are trying to upload) is too large. If you are making a GET request,
then the reply body (what you are trying to download) is too large. These
limits have been established by the Internet Service Provider who operates
this cache. Please contact them directly if you feel this is an error.

Your cache administrator is webmaster."

...this new error message appears instead (also enclosed in quotation
marks):

"413. That's an error.
Your client issued a request that was too large. That's all we know."

As before, Google Chrome is the ONLY browser to encounter this error! I've
repeated the same experiment with IE8, Opera Version 12, Build 1467, and
Mozilla Firefox 14.0.1 and THEY ALL passed with flying colors. The only
failure here is Google Chrome!!! It really is a letdown to have to report
this problem to you once more since I truly expect Chrome to learn from its
mistakes. Yet here it is again. Yes, I expect you to remedy the problem
PERMANENTLY! But seeing that before the year is out, that a similar
error condition exists ONLY IN CHROME that was just reported back in June
2012, I'm truly perplexed. Why would you fix something and then have it
fail less than 6 months later? An even better question is why do other
browsers get this issue right and Chrome terribly wrong--repeatedly? To say
I'm disappointed is an understatement. Please get it right this time.

Absolutely disappointed,

***@gmail.com

Attachments:
Error_413.JPG 68.1 KB
Firefox_No_Error_413.JPG 144 KB
IE8_No_Error_413.JPG 150 KB
Opera_No_Error_413.JPG 142 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-10-22 10:37:42 UTC
Permalink
Comment #16 on issue 131775 by ***@gmail.com: ERROR The requested URL
could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

Dear All,

My apologies: I've attached the wrong screenprint for Chrome
(Error_413.JPG). The correct one (Chrome_Error_413.JPG) is attached
herewith.

Sorry for any inconvenience this error might have caused.

***@gmail.com

Attachments:
Chrome_Error_413.JPG 64.7 KB
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
c***@googlecode.com
2012-10-22 11:28:10 UTC
Permalink
Updates:
Status: WontFix

Comment #17 on issue 131775 by ***@chromium.org: ERROR The requested
URL could not be retrieved The request or reply is too large.
http://code.google.com/p/chromium/issues/detail?id=131775

This is not a Chrome issue. Looking at the net-internals dumps you posted
before, we are sent an incredible 316 Set-Cookie headers sent in response
to a single request. This results in us very large HTTP request, which the
server is complaining about.

Chrome has a higher limit on cookies before it starts arbitrarily throwing
them out, which is probably the reason you only see the error with Chrome.
Since you're using a proxy, that is the most likely cause of the issue.
You can try clearing all cookies (Since the beginning of time), but the
issue will probably come back until you get rid of the broken proxy.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
Loading...