Does anyone have a good "recipe" for setting up nginx to proxy or redirect users to use a nicer base URL, IOW to change https://projects.commercialservices.com/servicedesk/customer/portal/3 to something better, like https://helpdesk.commercialservices.com?
I tried the setup below, and while it does work, the user gets redirected by JIRA via a 303 and the URL changes to the long form.
server { listen 80; server_name helpdesk.*; access_log off; client_max_body_size 10M; return 301 https://helpdesk.commercialservices.com$request_uri; } server { listen 443 ssl; server_name helpdesk.commercialservices.com; access_log off; client_max_body_size 10M; ssl_certificate /######; ssl_certificate_key /######; location / { proxy_pass http://localhost:8080/servicedesk/customer/portal/3; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }
Tom, I have not. The user-friendly, root URL seemed good enough to get people started on the portal.
hi,
your solution hide original JIRA address and stay on: helpdesk.commercialservices.com.
i can't get it work that way.
thanks. norbert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The above shouldn't "hide" anything. For example, on my server, I can still reach JIRA via IP and other valid addresses/URLs. The only reason I use nginx is to (try to) present users with a user-friendly URL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.