So putting all together: we would need a access-component available for each page - if its secured we would have to access it via https and vice versa, else it would have to call a redirect to itself - all tapestry links should respect this setting and transform themself into the right scheme (http or https) automatically, so we wouldnt have to mess with the links to a page we wanted unsafe yesterday but today safe
however, we mustnt assume that 80 and 443 are the right ports, leading to the possiblity that the ports should be made changeable to whatever we need via hivemind - so we wouldnt have to care if we use the 2 standards (as 80 and 443 is default) and may change it if we need to however the display of https:443 or http:80 is ugly and we also dont want that! - so display that should be only if its not the default 2 ones (eg: https:801) did i miss anything ? Regards, Korbinian > -----Ursprüngliche Nachricht----- > Von: Fernando Padilla [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 5. April 2006 16:42 > An: Tapestry users > Betreff: 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? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
