On Tue, 2011-12-20 at 16:20 +0530, 0 wrote: > > front end is nginx listening on port 80 with a name virtual host > proxied > > to another webserver that actually runs the app on ports 8000 > onwards. > > This works fine as long as there is an internet connection - if > there is > > no internet connection, firefox barfs saying it cannot access the > net > > and find the site. There is no problem if I run an IP based virtual > host > > - but then I can only run one site at a time. In the old days > firefox > > had an option like - 'these are local sites, no need for internet'. > (or > > was that netscape? Any suggestions? > > Did you try with good old telnet ? Also, check whether you have any > proxies in firefox settings. In your case, since there are multiple > levels before you get the page, it might be better to debug step by > step > using curl (or something similar). > > If you know the remapping rules, you should first try sending the > requests to your app running on port 8000+ with proper headers and > make > sure it works. It might not a simple task but might help in debugging > greatly. And, If your app works, then you can try checking whether > nginx > rules are correct and whether the remapping to your app works > correctly.
let us make it simpler. Forget all the virtual host stuf and nginx etc. To replicate the bug just do this on a standalone machine: 1. in /etc/hosts add the line: 127.0.0.1 mysite.web 2. make sure apache is running and listening on 80 3. In any browser try to access mysite.web - you will either get the default apache page or whatever you have put as your default site. 4. Disconnect your internet connection 5. Clear browser cache 6. try to access mysite.web (you can ping it, but cannot access it through a browser - I have tried firefox and links) -- regards Kenneth Gonsalves _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
