angularjs - I have a proxied node app on port 9000 working well, but after login the port shows up why? -


my angular-fullstack express app working well. served on port 9000 through nginx using proxy_pass https://example.com:80 -> https://example.com:9000. when new user looks https://example.com routed https://example.com/login expect. however, once login, whey see url: https://example.com:9000 on firefox. , on chrome see: https://example.com:9000/# ??? why in world port showing , why # appearing?

in case nginx settings blame proxy_pass, here are:

  location / {     proxy_set_header   x-real-ip $remote_addr;     proxy_set_header   host      $host;     proxy_pass https://127.0.0.1:9000;     proxy_http_version 1.1;     proxy_set_header upgrade $http_upgrade;     proxy_set_header connection "upgrade";     proxy_set_header x-forwarded-for $proxy_add_x_forwarded_for;     proxy_set_header x-nginx-proxy true;    } 

is there simple way tell nginx hide port on response, , why # appear on chrome?

your insight appreciated!

to address port number showing up, might need set proxy_redirect directive in nginx config. linked doc states, proxy_redirect

sets text should changed in “location” , “refresh” header fields of proxied server response

which port number being added in.

as #, that's application specific - you're going have @ code figure out why.


Comments

Popular posts from this blog

jquery - How do you format the date used in the popover widget title of FullCalendar? -

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -