使用Nginx仅将桌面流量重定向到HTTPS

使用Nginx仅将桌面流量重定向到HTTPS,nginx,nginx-reverse-proxy,nginx-config,Nginx,Nginx Reverse Proxy,Nginx Config,我试图强制将桌面(非移动)流量重定向到HTTPS。对于这个特定的域,我使用Nginx,然后将代理反向到Apache。以下是我当前的配置: server { server_name example.com www.example.com; location / { proxy_pass http://EXAMPLE_IP:8080; proxy_set_header Host $host; proxy_set_header X-Re

我试图强制将桌面(非移动)流量重定向到HTTPS。对于这个特定的域,我使用Nginx,然后将代理反向到Apache。以下是我当前的配置:

server {
    server_name example.com www.example.com;

    location / {
        proxy_pass http://EXAMPLE_IP:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
使用此Nginx代码:

  • 参观工作
  • 参观工作
如何添加逻辑来执行用户代理检测和正确的重定向


我确实发现了这段代码来检测非移动通信量-

我解决了它!以下是对我有效的方法:

### Testing if the client is a mobile or a desktop.
### The selection is based on the usual UA strings for desktop browsers.

## Testing a user agent using a method that reverts the logic of the
## UA detection. Inspired by notnotmobile.appspot.com.
map $http_user_agent $is_desktop {
    default 0;
    ~*linux.*android|windows\s+(?:ce|phone) 0; # exceptions to the rule
    ~*spider|crawl|slurp|bot 1; # bots
    ~*windows|linux|os\s+x\s*[\d\._]+|solaris|bsd 1; # OSes
}

server {
    server_name example.com www.example.com;

    location / {
        proxy_pass http://EXAMPLE_IP:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
    if ($is_desktop) {
        set $redirection A;
    }

    if ($host = www.example.com) {
        set $redirection "${redirection}B";
    } # managed by Certbot


    if ($host = example.com) {
        set $redirection "${redirection}B";
    } # managed by Certbot


    if ($redirection = AB) {
        return 301 https://$host$request_uri;
    }

    server_name example.com www.example.com;

    listen 80;
    location / {
        proxy_pass http://EXAMPLE_IP:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}