[Seaside] Deploying problem with serverPath and nginx

[Esteban A. Maringolo]

Mariano:

A question for your question: why do you configure Seaside to serve
HTTPS (or at least at port 443)?

Why not offload all the TLS/SSL work to nginx frontend and serve plain
old HTTP.


Regards,


Esteban A. Maringolo


2014/1/6 Mariano Martinez Peck <marianopeck at gmail.com>:
> Hi guys,
>
> I am having a problem trying to deploy an app with nginx. Say my seaside app
> is registered with a name 'myApp' and I am deploying it at:
> https://localhost/myApp and I want to have it under
> 'https://localhost/test'. I am using nginx and FastCGI (Gemstone).
>
> Notice that I don't want to register the app with a different name ('test'
> in this example). I want the app to continue being deployed with 'myApp'
> name. I just change to change the URL suffix.
>
> In seaside side I did:
>
> app
>     preferenceAt: #serverProtocol put: 'https';
>     preferenceAt: #serverHostname put: 'localhost';
>     preferenceAt: #serverPort put: 443;
>      preferenceAt: #serverPath put: '/test'.
>
> And in nginx I have:
>
>
> location /test {
>        try_files $uri @seasideTest;
> }
>
>
>         location @seasideTest {
>           include fastcgi_params;
>           fastcgi_pass seaside;
>
>         }
>
>
>       upstream seaside
>       {
>         server localhost:9001;
>       }
>
>
> However, if I browse  'https://localhost/test' I get a "/test not found".
> And in nginx logs I get "2014/01/06 10:51:06 [info] 43449#0: *31 client
> prematurely closed connection while reading client request line, client:
> 127.0.0.1, server: localhost"
>
> Any idea what I am doing wrong? Maybe I still need a rewrite of the url from
> '/test' to '/myApp' ? ...
>
> Thanks in advance,
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>