Jonathan Matthews Wrote: ------------------------------------------------------- > Fortunately, this being a *public* *mailing* *list*, and Francis > (along with almost every other subscriber) giving his time, experience > and opinions for free, you are definitely no worse off than when you > started. > > Actually, however, you're demonstrably better off, as Francis has both > attempted to help you go through the kind of troubleshooting process > that will serve you well if you apply it (Message-ID > 20140525132809.gn16...@daoine.org) and ... > > > I think what I asked is > > very clear and simple: > > How do I avoid repeating a segment of configuration code assigned to > @php > > into various locations: > > .... he has given you the answer to this question - that you clearly > thought you began by asking, but didn't. In Message-ID > 20140531112745.gz16...@daoine.org. > > HTH.
I'm sorry, I did not understood nothing. Can you provide an example of how to avoid repeating the php configuration through @php location? IMO the logic presented is clear: define a @php location and call it in other locations with try_files, like explained into Nginx documentation. In my case the end result is unexpected, the php file contents will be downloaded, instead of being executed. This works: http://pastie.org/private/5gkl1pti1co0onzhgb8jpg This does not: http://pastie.org/private/iuz58naozk6xo92ukqmwsg Posted at Nginx Forum: http://forum.nginx.org/read.php?2,250342,250655#msg-250655 _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
