You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ernest Monklitch (JIRA)" <de...@tapestry.apache.org> on 2008/03/17 18:10:24 UTC
[jira] Created: (TAPESTRY-2270) PageLink loses port from the url
PageLink loses port from the url
--------------------------------
Key: TAPESTRY-2270
URL: https://issues.apache.org/jira/browse/TAPESTRY-2270
Project: Tapestry
Issue Type: Bug
Affects Versions: 5.0.11
Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit.
Reporter: Ernest Monklitch
Priority: Blocker
Fix For: 5.0.12
After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
We don't use the standard ports when developing and there are is few apps on production with non-standard ports too, so this must be fixed. Secured annotation broke this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Issue Comment Edited: (TAPESTRY-2270) PageLink loses port
from the url
Posted by "Filip S. Adamsen (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579523#action_12579523 ]
fsa edited comment on TAPESTRY-2270 at 3/17/08 10:34 AM:
----------------------------------------------------------------------
This is indeed a side effect of the introduction of the Secure annotation. Host name and ports are now handled by the BaseURLSource service, which you should override if you use non-standard ports etc. You should probably override it anyhow, just in case. Details are in the docs here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/secure.html.
was (Author: fsa):
This is indeed a side effect of the introduction of the Secured annotation. Host name and ports are now handled by the BaseURLSource service, which you should override if you use non-standard ports etc. You should probably override it anyhow, just in case. Details are in the docs here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/secure.html.
> PageLink loses port from the url
> --------------------------------
>
> Key: TAPESTRY-2270
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2270
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.11
> Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit. Spring controls the ports and https / http scheme.
> Reporter: Ernest Monklitch
> Priority: Blocker
> Fix For: 5.0.12
>
>
> After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
> We don't use the standard ports when developing and there are few apps on production with non-standard ports too, so this must be fixed. Secure -annotation broke this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-2270) PageLink loses port from the url
Posted by "Ernest Monklitch (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ernest Monklitch updated TAPESTRY-2270:
---------------------------------------
Description:
After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
We don't use the standard ports when developing and there are few apps on production with non-standard ports too, so this must be fixed. Secure -annotation broke this?
was:
After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
We don't use the standard ports when developing and there are is few apps on production with non-standard ports too, so this must be fixed. Secured annotation broke this?
Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit. Spring controls the ports and https / http scheme. (was: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit.)
> PageLink loses port from the url
> --------------------------------
>
> Key: TAPESTRY-2270
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2270
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.11
> Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit. Spring controls the ports and https / http scheme.
> Reporter: Ernest Monklitch
> Priority: Blocker
> Fix For: 5.0.12
>
>
> After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
> We don't use the standard ports when developing and there are few apps on production with non-standard ports too, so this must be fixed. Secure -annotation broke this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-2270) PageLink loses port from the url
Posted by "Ernest Monklitch (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ernest Monklitch resolved TAPESTRY-2270.
----------------------------------------
Resolution: Invalid
And once again my fingers type faster than my brains think. Got to get that tenth cup of coffee now... :)
> PageLink loses port from the url
> --------------------------------
>
> Key: TAPESTRY-2270
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2270
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.11
> Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit. Spring controls the ports and https / http scheme.
> Reporter: Ernest Monklitch
> Priority: Blocker
> Fix For: 5.0.12
>
>
> After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
> We don't use the standard ports when developing and there are few apps on production with non-standard ports too, so this must be fixed. Secure -annotation broke this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2270) PageLink loses port from the url
Posted by "Filip S. Adamsen (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579523#action_12579523 ]
Filip S. Adamsen commented on TAPESTRY-2270:
--------------------------------------------
This is indeed a side effect of the introduction of the Secured annotation. Host name and ports are now handled by the BaseURLSource service, which you should override if you use non-standard ports etc. You should probably override it anyhow, just in case. Details are in the docs here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/secure.html.
> PageLink loses port from the url
> --------------------------------
>
> Key: TAPESTRY-2270
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2270
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.11
> Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit. Spring controls the ports and https / http scheme.
> Reporter: Ernest Monklitch
> Priority: Blocker
> Fix For: 5.0.12
>
>
> After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
> We don't use the standard ports when developing and there are few apps on production with non-standard ports too, so this must be fixed. Secure -annotation broke this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-2270) PageLink loses port from the url
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2270:
-------------------------------------------
Fix Version/s: (was: 5.0.12)
> PageLink loses port from the url
> --------------------------------
>
> Key: TAPESTRY-2270
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2270
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.11
> Environment: Tomcat 6.0.16 and Tomcat 6.0.14 tested on vista 64bit. Spring controls the ports and https / http scheme.
> Reporter: Ernest Monklitch
> Priority: Blocker
>
> After upgrading to 5.0.11 we began to experience some strange behaviour, but quite fast we noticed that PageLinks are redirecting everything to 80 or 433. (There actually isn't any port in the url, just http or https.) As long as the servers use those ports everything is fine.
> We don't use the standard ports when developing and there are few apps on production with non-standard ports too, so this must be fixed. Secure -annotation broke this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org