Chrome Error 501 Err_insecure_response
Contents |
from GoogleSign inHidden fieldsSearch for groups or messages
frames Starred by 29 users Reported by rocky.pa...@gmail.com, Jun 29 2011 Back to list Status: WontFix Owner: ---- Closed: Aug 2011 Components: Internals Internals>Network>SSL UI UI>Browser>TabContents OS: All Pri: 2 Type: Bug Restrict-AddIssueComment-EditIssue Restricted Only users with EditIssue permission may comment. Sign in to add a comment Chrome Version : 13.0.782.32 OS Version: 6.1 (Windows 7, Windows Server 2008 R2) What steps will reproduce the problem? 1. enter a site with a link to an URL with http://productforums.google.com/d/topic/chrome/Hd7MIpnXBVA a mismatched SSL cert inside a frame. 2. click on link. instead of chromes SSL warning page, error 501 text. What is the expected result? Inside the frame, the link should show the "This is probably not the site you are looking for" page, with a continue button. What happens instead? The Error 501 (net::ERR_INSECURE_RESPONSE): Unknown error shows. https://bugs.chromium.org/p/chromium/issues/detail?id=87957 Since its in a frame, there is no way to proceed with the link if that is the desired action. In our development environments, we are using framesets with a mismatched SSL cert. The expectation to click a proceed button is fine, however chrome is simply unusable because the 501 error page with no continue button shows instead of the SSL warning page. Comment 1 by willchan@chromium.org, Jun 29 2011 Processing Labels: -Area-Undefined -OS-Windows Internals-Network-SSL OS-All Comment 2 by yabdulka...@gmail.com, Jul 11 2011 Processing I see the same thing in Chrome 13.0.782.41 This webpage is not available The webpage at https://somedomain/someapp/Client/login.asp?librarycenter=no&serverprotocol=https might be temporarily down or it may have moved permanently to a new web address. Error 501 (net::ERR_INSECURE_RESPONSE): Unknown error. Comment 3 by chris.de...@gmail.com, Aug 13 2011 Processing Same issue with Chrome 14.* beta and Chrome 15.0.849.1 dev. This is a priority bug because it requires us to fire up Firefox or Internet Explorer to use the affected web sites. Comment 4 by rsleevi@chromium.org, Aug 13 2011 Processing Labels: Area-UI Area-Internals Fe
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business http://stackoverflow.com/questions/8418019/can-google-chrome-be-used-on-a-local-dev-server-with-an-invalid-ssl-cert Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Can Google Chrome be used on a local dev server with an invalid SSL cert? up vote 6 down vote favorite 2 Our application chrome error runs within a frameset that uses one visible frame to show content and two others to handle communication with the server. I did not design this and have no power to change it now. The problem is that my local machine does not have a valid SSL certificate (it's self-signed), so accessing it and trying to login pops an 'invalid certificate' error. In IE and FF I am able to simply click a button to chrome error 501 continue. However, I just started trying to test with Chrome and it seems to stop me dead with: Error 501 (net::ERR_INSECURE_RESPONSE): Unknown error. There is no option to continue. There also doesn't appear to be anything in the options menu to add localhost as a trusted site, though I may have missed something. Does anyone know a way around this? Disabling SSL locally won't be very easy and risks me forgetting to enable it for deployment. Any other thoughts? Thanks. google-chrome ssl share|improve this question asked Dec 7 '11 at 15:39 Nicholas 59721029 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted What I would recommend is to add the self-signed certificate to Chrome manually rather than trying to make localhost a trusted site. It looks like there are a couple ways to accomplish this. Here is one forum thread that discusses the issue, but I think it boils down to: If you are on Windows, install the certificate in IE. The linked thread explains this process in more detail, but it looks like you go to the site in IE, click "Continue" or similar, then right-click the certificate error button to the right of the URL bar and follow the prompts. (If that doesn't work, here's a question that I believe addresses the issue.) More recent vers