On 23 June 2016 at 19:43, Mark Thomas <ma...@apache.org> wrote: > On 23/06/2016 17:56, Lyallex wrote: >> I'm trying to understand why a recent change in 7.0.70 has been done >> the way it has. >> The change makes absolutely no sense to me and I need to ask the >> implementer why in the name of sanity he did what he did. >> I'm talking to you markt whoever you are :-) >> >> Where should I ask the question? dev list? >> >> I couldn't care less how much shouting ensues, I just need to get some sleep. > > How about you cut the attitude and just ask your question?
OK, I will. To give this some context and with the greatest respect to a dedicated committer none of what follows is intended as criticism it's just that I think the current solution to 59399 need rethinking My commercial site has been up for years, there are links dating back years that refer to the old http scheme I have no control over this, now, whenever I get a hit from an 'old' link I need to force the switch to https, lots of sites have this probem and need a solution, it has nothing whatsoever to do with dabases in any way shape or form. So, https://bz.apache.org/bugzilla/show_bug.cgi?id=59399 What has the status code returned when switching from http -> https got to do with a Realm? http://tomcat.apache.org/tomcat-7.0-doc/realm-howto.html <cite> "A Realm is a "database" of usernames and passwords that identify valid users of a web application .. " </cite> Or: What has the status code returned when switching from http -> https got to do with a database of usernames and passwords? https://tomcat.apache.org/tomcat-7.0-doc/config/realm.html JDBCDatabaseRealm attrbute: transportGuaranteeRedirectStatus <cite> The HTTP status code to use when the container needs to issue an HTTP redirect to meet the requirements of a configured transport guarantee. The prpvoded status code is not validated. If not specified, the default value of 302 is used. </cite> I just don't get why this is here furthermore https://bz.apache.org/bugzilla/show_bug.cgi?id=59399 <cite> Mark Thomas 2016-06-15 11:12:11 UTC This has been implemented as a new option in the Realm and will has implemented in: - 9.0.x for 9.0.0.M9 onwards - 8.5.x for 8.5.4 onwards - 8.0.x for 8.0.37 onwards - 7.0.x for 7.0.70 onwards </cite> Which Realm(s)? only JDBCDatabaseRealm has the attribute but your comment seems to imply that all Realms have it (transportGuaranteeRedirectStatus) In which case surely it should be a common attribute and (I'm guessing here) the functionality be included in the base class for Realm What happens if I don't use JDBCDatabaseRealm, does that mean I can't configure the switchover status code. What happens if I write my own Realm? In the 'good old days' it was common practice to only switch to https during or after signing in to an application, networks were slow and encryption takes time, now networks are faster and the overhead isn't such an issue. Entire sites now use the https scheme, I know mine does. I can see a situation where, because the mighty Google says it must be so, even an entirely static site with no database and no manager will be served up under https. How is such a site suppose to implement https? FYI I have it in black and white, from a Google webaster forum responder that, in the event of a tie between two pages in a ranking calculation, the https scheme would produce a ranking signal that would elevate the https page above the non https page in the resulting rankings. Once again this is not intended as criticsm of a dedicated and prolific committer With respect Lyallex > > If you are ever unsure where to ask, use the users list. > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
