Does anyone else get error in code and Oops something went wrong when using Chrome Browser?
I have a Windows 10 Pro v 21H1 64bit 8gb RAM box and using Chrome version 92.1.4515.107.
If I do any search, and then click on the subjects name in the first column of the results, it throws a Code Error, and then a page with Ooops, Something has gone wrong. and can never get to the records.
I have tried stopping all the Chrome Extensions, Cleared Cache, and rebooted with out any change in the error.
This only happens with Chrome. MS Edge is OK, as is Firefox.
Best Answer
-
Thanks. Clearing all cache, cookies and browsing data seems to have cleared that up.
0
Answers
-
The OOPS something went wrong could happen if you click on a link that is only for people who are members of the community and you have not signed on. Another cause could be a timing problem where Chrome assumes the page is not there if it does not get a response to the get in a certain amount of time. Since it is only happening in Chrome you may want to switch to Edge or Firefox and import your data from Chrome.
Firefox allows you to adjust the timeout value while Chrome does not.
0 -
@TerrySilval Thanks for the comment, but for other reasons I changed away from Firefox, Opera and Edge because of different issues with each browser and Financial and Banking websites. When I get the Error in Code in Chrome, this is the view page source at that time :
Line wrap
<!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1><hr class="line" /><p><b>Type</b> Exception Report</p><p><b>Message</b> Request header is too large</p><p><b>Description</b> The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).</p><p><b>Exception</b></p><pre>java.lang.IllegalArgumentException: Request header is too large org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:781) org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:936) org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:607) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:525) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1629) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.lang.Thread.run(Thread.java:748)</pre><p><b>Note</b> The full stack trace of the root cause is available in the server logs.</p><hr class="line" /><h3>Apache Tomcat/8.5.63</h3></body></html>
Now, all I do is click on a name or link! Familysearch is rejecting the data sent. Request Header is too large? I'm not sure that the timeout will have any influence on this, but I don't fully understand all the apache handling as that is on FS server side?
0 -
You may get error messages when your browser is clogged with Temporary internet files (cookies) . doing an internet search for how to clean cookies from Chrome may be worth considering.
0
