[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
