Nginx serving the wrong url?

I’m not sure what exactly
“/var/www/https:/secure.domain.com/index.html” is (should be
/var/www/index.html) How can I correct this?

2011/01/28 17:20:05 [error] 15415#0: *1117703
“/var/www/https:/secure.domain.com/index.html” is not found (2: No
such file or directory), client: 119.110.28.211, server:
secure.domain.com, request: “HEAD /https://secure.domain.com/
HTTP/1.1”, host: “secure.domain.com
2011/01/28 17:26:44 [error] 15413#0: *1119352
“/var/www/https:/secure.domain.com/index.html” is not found (2: No
such file or directory), client: 89.119.24.23, server:
secure.domain.com, request: “HEAD /https://secure.domain.com/
HTTP/1.1”, host: “secure.domain.com
2011/01/28 18:26:12 [error] 15415#0: *1134480
“/var/www/https:/secure.domain.com/index.html” is not found (2: No
such file or directory), client: 70.41.141.44, server:
secure.domain.com, request: “HEAD /https://secure.domain.com/
HTTP/1.1”, host: “secure.domain.com

server {
    server_name secure.domain.com;
    listen       443;
    listen       [::]:443 default ipv6only=on;
    gzip         on;
    gzip_comp_level  1;
    #gzip_buffers   32  128k;

    gzip_types      text/plain text/html text/css

application/x-javascript text/xml text/javascript;
# GZIP module, stops the cpu usage for compressing the files
all the time time.
error_log logs/ssl.error.log;
gzip_static on;
gzip_http_version 1.1;
gzip_proxied any;
gzip_disable “msie6”;
gzip_vary on;
ssl on;
ssl_ciphers RC4:ALL:-LOW:-EXPORT:!ADH:!MD5;
#ssl_prefer_server_ciphers on;
#keepalive_requests 280;
#keepalive_timeout 5;
#ssl_session_cache shared:SSL:10m;
#ssl_session_timeout 1m;
keepalive_timeout 0;
ssl_certificate /root/server.pem;
ssl_certificate_key /root/ssl.key;

       location / {
            root   /var/www;
            index  index.html index.htm index.php;
        }

}

On Mon, Feb 28, 2011 at 12:43:29PM +1300, Ryan B wrote:

Hi there,

I’m not sure what exactly
“/var/www/https:/secure.domain.com/index.html” is (should be
/var/www/index.html) How can I correct this?

Find the Referer: page, the place where these clients found this link,
and change it to point to

https://secure.domain.com/

instead of

/https://secure.domain.com/

request: “HEAD /https://secure.domain.com/
HTTP/1.1”, host: “secure.domain.com

That is the request that is being received.

Good luck,

f

Francis D. [email protected]

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs