nginx passenger standalone empêche proxy_pass sur le sous-répertoire

Question

J'utilise nginx comme proxy inverse pour le serveur de rails autonomes. Je dois configurer l'emplacement racine / sur le port autonome du passager (5000), mais peu d'autres sous-répertoires doivent être desservis par "pure" nginx. Je suis en train de configurations comme

server { 
    listen 443; 

    root /path/to/rails/public; 

    server_name example.com; 

    ssl on; 
    # ... some ssl config 

    # this is used for passenger standalone on port 5000 
    location/{ 
      proxy_pass https://127.0.0.1:5000; 
      proxy_http_version 1.1; 
      proxy_set_header Host $http_host; 
      proxy_set_header Upgrade $http_upgrade; 
      proxy_set_header Connection $connection_upgrade; 
      proxy_buffering off; 
    } 

    # this is not passenger standalone! 
    location /subdir { 
      proxy_pass https://127.0.0.1; 
      auth_basic "Restricted access area authorization needed."; 
      auth_basic_user_file /path/to/.htpasswd; 
    } 

}

mais https://example.com/subdir/ retour toujours erreur 404. Des conseils pour le réparer?

Answer 1

Déplacez la directive d'emplacement pour /subdir au-dessus de la direction de l'emplacement racine. Les chemins de requête sont appariés dans l'ordre défini dans la configuration.

server { 
    listen 443; 

    root /path/to/rails/public; 

    server_name example.com; 

    ssl on; 
    # ... some ssl config 

    # this is not passenger standalone! 
    location /subdir { 
      proxy_pass https://127.0.0.1; 
      auth_basic "Restricted access area authorization needed."; 
      auth_basic_user_file /path/to/.htpasswd; 
    } 
    # this is used for passenger standalone on port 5000 
    location/{ 
      proxy_pass https://127.0.0.1:5000; 
      proxy_http_version 1.1; 
      proxy_set_header Host $http_host; 
      proxy_set_header Upgrade $http_upgrade; 
      proxy_set_header Connection $connection_upgrade; 
      proxy_buffering off; 
    } 
}