[Seaside-dev] Seaside application with HTTPS

[Philippe Marschall]

2009/7/6 Christopher Schuster <cs at livoris.de>:
> Hi list,
>
> I want to use my Seaside application with http and https simultaneously.

You use Seaside 2.9, right?

>     This works good apart from links. Registering a callback uses
> baseUrl from the WAEntryPoint. The returned URL uses the serverProtocol
> that is configured in the preferences of the entrypoint.
>
> It would be better if the scheme would depend on the actual request
> scheme. My suggestion is adding the method
>
> WARequest>>#isSSL
>        ^ false
>
> And adding a line to the method
>
> WAUrl>>#takeServerParametersFromRequest: aRequest
>        ...
>        aRequest isSSL ifTrue: [ self scheme:  'https' ]
>
> Alternatively, "isSSL" can be an instance variable in WARequest.

I would prefer this option over having multiple subclasses.

> (I am
> using AJP to enable SSL and it's no problem to set this variable
> depending on the AJPRequest.)

Yeah, it's easy with AJP. I'm wondering what we should do for Apache
frontend case, look at x-forwarded-for?

Cheers
Philippe