On Sun, Dec 23, 2012 at 12:00 AM, Gulaholic <nginx-forum@nginx.us> wrote:
> Hi,
>
> Thank you for your response.
>
> Here is my Nginx conf:
> user www-data;
> pid /var/run/nginx.pid;
>
> events {
> multi_accept on;
> worker_connections 1024;
> }
>
> http {
> access_log off;
> default_type application/octet-stream;
> server_names_hash_bucket_size 64;
> server_tokens off;
> }
>
>
> server {
> listen 80;
> server_name domain.tld;
> access_log off;
> error_log /home/userdirectory/http/logs/beta.crunchy.tk.log;
> index index.html index.php;
> root /home/userdirectory/http/hosts/beta.crunchy.tk;
> }
>
>
> Here is the output of curl -i http://domain.tld:
> HTTP/1.1 302 Moved Temporarily
> Server: nginx
> Date: Sat, 22 Dec 2012 16:57:20 GMT
> Content-Type: text/html
> Transfer-Encoding: chunked
> Connection: keep-alive
> Set-Cookie: CMSSESSIDddd38826=ce5tkr97o1gm2vj7kkumuevur5; path=/
> Expires: Sat, 22 Dec 2012 19:57:20 GMT
> Cache-Control: public, max-age=10800
> Last-Modified: Sat, 10 Nov 2012 16:14:56 GMT
> Location: https://domain.tld
>
> As you can see the location is using https already.
>
> What can you see from these information?
>

Your php application caused this. You can trick it into thinking it's
https by sending relevant headers or just check the application.

And I think you cut too much information from your config.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx