DNS lookup failed"Īnd that says that the browser did not know where nginx was. if the browser makes the request of nginx. So: they both say that if the request gets to nginx, nginx responds as > root at > content of /tmp/www/one/index.html On Thu, at 04:33:04PM +0200, Pascale Camille wrote: One might have caused things notįrom francis at Thu Aug 14 17:23:20 2014 I'd say that the problem was using "if" inside "location" without > So, the problem was the second IF in the same location. Or compile-time differences which matter.) (And the "nginx -V" output can be useful too, in case there are version That way, everyone testing things is looking at the same thing. Small config that reliably shows the problem you encounter (and whichĬontains no private information), and then copy-paste exactly what is Yes, it is always best to create a scratch system with a > I didn't move a second IF there, and again, did not pay enough attention toĪh, right. That's why it worked in a separate location. > In my example (before posting it here) I've dropped the second IF in the It is only "if inside location" which needs care. > should re-read it every time I want to use IF. > Actually, the second problem is described in this document too, I think I Subject: add_header is not working in certain locations Message-ID: i just did again and remembered error,įrom francis at Thu Aug 14 17:16:55 2014įrom: francis at (Francis Daly) Hi, you may find this overkill configuration helpful:įrom lists at Thu Aug 14 14:51:44 2014įrom: lists at (Pascale Camille)įrom lists at Thu Aug 14 15:55:18 2014 DNS lookup failed"Īnd /nil or what else gives įrom nginx-forum at Thu Aug 14 14:47:28 2014
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |