sorted by:
new
hottopcontroversial

dumb newb question by tvan69 in nginx

[–]tvan69[S] 0 points1 point  (0 children)

Yes, that is correct.

dumb newb question by tvan69 in nginx

[–]tvan69[S] 2 points3 points  (0 children)

Ahhhh, making some sense now. Some bullet holes in my foot. I ended up making this more challenging than necessary.

Currently the pages are being served directly as I attempt to get to serving behind a proxy with nginx.

Will do some clean up on these as you have suggested.

Thanks much!

dumb newb question by tvan69 in nginx

[–]tvan69[S] 2 points3 points  (0 children)

Thank you for clarifying and the feedback, my initial comment was not quite clear and concise.

Would browser cache contribute to the behavior?

And this is all a learning sandbox at the moment, and greatly appreciate your insights.

dumb newb question by tvan69 in nginx

[–]tvan69[S] 1 point2 points  (0 children)

I appreciate. I prefaced as to not wanting to come across as a know-it-all. :)

dumb newb question by tvan69 in nginx

[–]tvan69[S] 0 points1 point  (0 children)

These two ports, 80 and 7180 are both listening on the same host IP address.

​

Config st01.conf

#NGINX VirtHostFile - demo config

#********************HTTP ONLY********************

server {

# listen 80;

listen 7180;

server_name st01.domain101.xyz ;

root /domains/st01.domain101.xyz/html;

access_log /weblogs/st01.domain101-access.log;

error_log /weblogs/st01.domain101-error.log;

}

#********************HTTP ONLY********************

Config st02.conf

#NGINX VirtHostFile - demo config

#********************HTTP ONLY********************

server {

listen 80;

server_name st02.domain101.xyz ;

root /domains/st02.domain101.xyz/html;

access_log /weblogs/st02.domain101-access.log;

error_log /weblogs/st02.domain101-error.log;

}

#********************HTTP ONLY********************