https://issues.apache.org/bugzilla/show_bug.cgi?id=50823
--- Comment #11 from Nathan Schulte <[email protected]> 2012-04-18 21:49:33 UTC --- (In reply to comment #10) > I am not sure that we need yet another directive if the default behavior is > OK. > But at least since we support SNI, the current behavior is just wrong. I agree; a new Directive isn't necessary so long as the default behavior is suitable, and the current default is not. > > I will also attempt to verify the HTTP 1.0 / 400 status patch. I effecting > > that patch, as well as removing the mischievous link would help immensely. > > Is > > returning a document with a script to sed -e 's/http:\/\//https:\/\//' > > window.location or document.URL and place it as the href of an anchor out of > > the question? > > That sounds like a good idea. This kind of dances around the issue, as with supporting SNI the server should/would/could be expected to already know this. I don't see anything wrong with it though, but I'm not sure how the Project views it. If having a script in the error page is allowable and if a redirect is deemed a better solution than suggesting the user might have meant HTTPS rather than HTTP, that could be done via script as well. I don't think a mandatory redirect assuming the client meant HTTPS rather than HTTP is correct, though. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
