I'm going nuts on this. Any help would be much appreciated.
The $request_uri
/h_32/w_36/test.jpg
needs to be routed to
/index.php/img/i/h_32/w_36/test.jpg
index.php will route the request to the "img" controller and "i" method,
then process the image and return it. However, my MVC works off of
Question on SF:
https://serverfault.com/questions/874730/convert-apache-mod-proxy-p-to-nginx-equivalent
My PHP MVC platform CodeIgniter performs routing based on the REQUEST_URI.
In Apache, you cannot change the REQUEST_URI environment variable. So, in
Apache, I made use of the [P]proxy flag. Sen
two versions are because they are the versions of openresty I am
trying to use this module in conjunction with.
Any guidance as to what would be causing these connections to never be
released would be very welcome.
Thank you,
Nathan Eloe
___
nginx mailing
Hello
We have a service for our customers that allows them to test their site
before they point their DNS to our servers. It works like this: we
configure their websites in our backend servers as usual, and we create
an entry in a zone we own. Say the customer's site is www.foo.com; we
give him a
Thanks a lot for the detailed answer, Yichun! I'll try to benchmark it,
estimate the db size, see if it fits in memory, etc.
Cheers,
Andre
signature.asc
Description: OpenPGP digital signature
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx
Hello
I'm considering the possibility of implementing a project using Nginx
and the Lua module. One of the requirements of the project is that the
code must use an embedded database such as SQLite. However, as known,
using the lua-sqlite3 library directly is not optimal because it would
block the
On 11/29/2013 10:13 AM, Maxim Dounin wrote:
> Connections are handled by worker processes. On SIGHUP, master
> process parses new configuration and spawns new worker processes
> (while old workers still handle requests). Then it asks old
> workers to gracefully shutdown. That is, all the time
Hello
In an apache webserver with many virtual hosts, a "reload" command can
cause a (quick) unavailability of the service while apache re-reads its
configuration files.
Does anyone have any experience with this on Nginx? Will sending it a
SIGHUP cause the main process to block and not be able to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2013 04:18 PM, Maxim Dounin wrote:
> If it doesn't work for you, you have another obvious option: fixing
> a backend will do the trick, too.
Yes, i think this is the optimal solution, but the back end is a
blackbox controlled by a vendor.
s:
>
> http://nginx.org/r/proxy_ssl_protocols
> http://nginx.org/r/proxy_ssl_ciphers
>
- --
- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nathan Lager, RHCSA, RHCE, RHCVA (#110-011-426)
System Administrator
11 Pardee Hall
Lafayette College, Easton, PA 18042
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am working on setting up an http reverse proxy in front of a
pre-packaged jetty server. The jetty server is a pre-configured
application, and not very flexible.
Here's the quick and dirty. I have nginx configured to listen on 443,
using its own SS
11 matches
Mail list logo