You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2012/10/19 11:10:13 UTC
[jira] [Created] (WICKET-4824) Reirect to HTTPS is using wrong port
80 if HttpsConfig with default ports 80/443 is used
Sven Meier created WICKET-4824:
----------------------------------
Summary: Reirect to HTTPS is using wrong port 80 if HttpsConfig with default ports 80/443 is used
Key: WICKET-4824
URL: https://issues.apache.org/jira/browse/WICKET-4824
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 6.1.1, 1.5.8
Reporter: Sven Meier
HttpsMapper#mapHandler() doesn't set the Url's port, if the desired protocol uses the standard port.
This leads to UrlRenderer choosing to the request's port as fallback (which is 80 before switching to https).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4824) Redirect to HTTPS is using wrong
port 80 if HttpsConfig with default ports 80/443 is used
Posted by "Sven Meier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier updated WICKET-4824:
-------------------------------
Affects Version/s: (was: 1.5.8)
Summary: Redirect to HTTPS is using wrong port 80 if HttpsConfig with default ports 80/443 is used (was: Reirect to HTTPS is using wrong port 80 if HttpsConfig with default ports 80/443 is used)
> Redirect to HTTPS is using wrong port 80 if HttpsConfig with default ports 80/443 is used
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-4824
> URL: https://issues.apache.org/jira/browse/WICKET-4824
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.1.1
> Reporter: Sven Meier
>
> HttpsMapper#mapHandler() doesn't set the Url's port, if the desired protocol uses the standard port.
> This leads to UrlRenderer choosing to the request's port as fallback (which is 80 before switching to https).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4824) Redirect to HTTPS is using wrong
port 80 if HttpsConfig with default ports 80/443 is used
Posted by "Sven Meier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier resolved WICKET-4824.
--------------------------------
Resolution: Fixed
Fix Version/s: 6.2.0
Assignee: Sven Meier
Port is now always set explicitly, it won't be rendered by UrlRenderer if not required
> Redirect to HTTPS is using wrong port 80 if HttpsConfig with default ports 80/443 is used
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-4824
> URL: https://issues.apache.org/jira/browse/WICKET-4824
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.1.1
> Reporter: Sven Meier
> Assignee: Sven Meier
> Fix For: 6.2.0
>
>
> HttpsMapper#mapHandler() doesn't set the Url's port, if the desired protocol uses the standard port.
> This leads to UrlRenderer choosing to the request's port as fallback (which is 80 before switching to https).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira