By default most urls are relative, yup. But when you want it to change
the scheme or port or host, it can't just change those things relatively
- it has to use an absolute url.
Detlef Schulze wrote:
Then that has changed from T3 to T4. T3 uses relative URLs not absolute ones
that may contain the port numbers.
I think you're wrong here because I simply don't think that T4 provides
absolute URLs only. You probably mean the URL that you see in the browser, but
that is not the URL that tapestry has provided (check the generated html)...
-----Original Message-----
From: Fernando Padilla [mailto:[EMAIL PROTECTED]
Sent: 05 April 2006 16:42
To: Tapestry users
Subject: Re: AW: https
yup, tapestry always provides the port number.. because again, letting
tapestry assume what port is the https port is just that assuming..
But yes the only port combination that I would allow tapestry to assume
would be 80/443 - as in if you are on http:80 <-> https:443. If it were
any non standard port, then we're in development and there is no
standard. But it was decided to be consitent, and thus explicit.
Detlef Schulze wrote:
... but if you define no port then the browser automatically connects to 443 if
it sees a leading https:// so that should work in production, or am I wrong?
Or does T4 always include the port number in the links?
-----Original Message-----
From: Fernando Padilla [mailto:[EMAIL PROTECTED]
Sent: 05 April 2006 16:32
To: Tapestry users
Subject: Re: AW: https
Just a warning. The 'scheme' parameter under 4.0 doesn't really work by
its self. You need to use the 'scheme' and 'port' parameters exposed
under 4.0.1.
If you have a url "http:80" and you just change the 'scheme' it turns
into an invalid url "https:80", since you can't have one web server with
both http and https on one port.
more babble:
You might then say, well can't it just assume the port? Well, no to be
exact, it can't. Under developement we use all kinds of ports, and
maybe for weird deployments ( hosted facilities, etc ), the ports might
be every which way too... So there is no way for the application to know
what port pairs you care about. And sadly there is no way through J2EE
for you to give the webapp that information, in a standard way. So you
have to manage the desired http/https ports through your application
configuration, and call them up whenever you want to have a particular
link explicitly jump through the http/https boundary.
Filip S. Adamsen wrote:
Natürlich. ; D
Check out the component reference for DirectLink, ExternalLink, PageLink
and ServiceLink - all these components have a "scheme" parameter. Set it
to "https" to enable https - this will force the creation of an absolute
URL if that scheme does not match that of the current request.
The scheme support is actually part of AbstractLinkComponent (because it
implements ILinkComponent), so if you have any application-specific link
components you can take advantage of this.
You might want to create a custom link component for your application to
handle whether a link should be secure or not.
Component Reference links:
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/DirectLink.html
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/ExternalLink.html
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/PageLink.html
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/ServiceLink.html
API Doc links:
http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/link/AbstractLinkComponent.html
http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/components/ILinkComponent.html
-Filip
Korbinian Bachl skrev:
Hi Filip,
could you point me and others to the doc regarding https in T4 ?
Thanks and Regards,
Korbinian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
