<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thanks! I followed you, until the proxy_pass. What is backend1, and where is it defined? I know it's something you made up, but how does it know about Apache, or Apache about it?<br class=""><div><blockquote type="cite" class=""><div class="">On May 12, 2016, at 17:56, Yuriy Medvedev <<a href="mailto:medvedev.yp@gmail.com" class="">medvedev.yp@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi, you can use vhost in Apache and configure proxy_pass in nginx configuration<div class="">For apache2 somthing like that</div><div class=""><div class=""><VirtualHost *:8080></div><div class=""> ServerName foo.bar</div><div class=""><br class=""></div><div class=""> DocumentRoot /home/sites/</div><div class=""> <Directory /home/sites/></div><div class=""> Order deny,allow</div><div class=""> Allow from all</div><div class=""> </Directory></div><div class=""><br class=""></div><div class=""> ErrorLog /home/sites/logs/apache_error.log</div><div class=""> CustomLog /home/sites/logs/apache_access.log combined</div><div class=""><br class=""></div><div class="">etc.......</div><div class=""></VirtualHost></div></div><div class="">For nginx</div><div class=""><div class="">server {</div><div class=""> listen 80;</div><div class=""> server_name foo.bar;</div><div class=""><br class=""></div><div class=""> access_log /home/sites/logs/nginx_access.log;</div><div class=""> error_log /home/sites/logs/nginx_error.log;</div><div class=""><br class=""></div><div class=""> location / {</div><div class=""> proxy_pass <a href="http://backend1/" class="">http://backend1</a>;</div><div class=""> etc.....</div><div class=""> }</div><div class="">}</div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2016-05-13 0:34 GMT+03:00 Alex Hall <span dir="ltr" class=""><<a href="mailto:ahall@autodist.com" target="_blank" class="">ahall@autodist.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class=""><div class=""><div class="">Hello all,<br class=""></div>Here's what I'm trying to do. I have two sites, <a href="http://sd1.mysite.com/" target="_blank" class="">sd1.mysite.com</a> and <a href="http://sd2.mysite.com/" target="_blank" class="">sd2.mysite.com</a>. The fun part is that sd1 is a Flask app, served by Nginx. However, sd2 is OSTicket, which must be served by Apache, it seems. Of course, Apache and Nginx can't listen to port 80 at the same time, and as this is a subdomain on a local, Windows DNS, I can't make <a href="http://sd2.mysite.com/" target="_blank" class="">sd2.mysite.com</a> point to myip:8080 or anything like that.<br class=""><br class=""></div>Thus, my best option appears to be this: Nginx listens to all incoming traffic on 80. If the request is for anything to do with sd1, it handles it just like it does now. However, if the request is for sd2, Nginx somehow hands off the request to Apache, then returns what Apache gives it back to the user.<br class=""><br class=""></div>I've heard that people use Apache and Nginx together, but I haven't found anyone who uses them to serve two subdomains, with Nginx as the "gateway" and handler of one subdomain, and Apache as the handler for the other subdomain. Is there any way to do this? Am I even making sense? Thanks for any ideas anyone has.<span class="HOEnZb"><font color="#888888" class=""><br clear="all" class=""><div class=""><div class=""><div class=""><div class=""><br class="">-- <br class=""><div class=""><div dir="ltr" class=""><div class=""><div class="">Alex Hall<br class=""></div>Automatic Distributors, IT department<br class=""></div><a href="mailto:ahall@autodist.com" target="_blank" class="">ahall@autodist.com</a><br class=""></div></div>
</div></div></div></div></font></span></div>
<br class="">_______________________________________________<br class="">
nginx mailing list<br class="">
<a href="mailto:nginx@nginx.org" class="">nginx@nginx.org</a><br class="">
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank" class="">http://mailman.nginx.org/mailman/listinfo/nginx</a><br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">nginx mailing list<br class=""><a href="mailto:nginx@nginx.org" class="">nginx@nginx.org</a><br class="">http://mailman.nginx.org/mailman/listinfo/nginx</div></blockquote></div><br class=""></body></html>