Bug #127
https transport is being converted to http with port 443
| Status : | Closed | Start : | ||
| Priority : | High | Due date : | ||
| Assigned to : | tobi - | % Done : | 0% |
|
| Category : | frontend | |||
| Target version : | Maybe Someday | |||
| Resolution : | fixed |
Description
Since upgrading to Typo HEAD (760) (and possibly since 2.5.6) and Tapestry 0.14.3, I'm having problems with URLs being translated improperly. I used HTTPS for the admin section, but was able to see the problem when viewing my posts using HTTPS as well.
When submitting a form in the admin section, I often get this:
-----
"Bad Request
"Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
"Hint: https://www.example.com/"
-----
I was on this page:
https://blog.dang.us/admin/categories/list
and ended up on this:
http://blog.dang.us:443/admin/categories/list
What's happened is that somewhere in the request, "https" has been changed to "http" and the port number 443 has been appended to the server address.
Another place to view this is to just go to a post in HTTPS and have a look at the trackback links. They are also in the form of "http://<url>:443/"
Here's an example. Go to this link and have a look at the trackback URL on the page:
https://blog.dangdev.com/articles/2005/11/26/rss-for-blogs-was-broken
It looks like this:
http://blog.dangdev.com:443/articles/trackback/32
Associated revisions
typo is now full static. The entire front end comes from static pages which are swept on commenting, trackbacks, new article posts and category changes.
This means we cannot do the "posted 25 minutes ago" business but we can easily serve in excess of 1k pages per second so this should be worth it.
applied static pages updates by Damien Pollet closes #127