Show all posts by user
A portal to and from the mailing list.
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> So either Django is not a compliant WSGI app or uWSGI is unable to mount > a standard WSGI application to the root location in nginx without using > magic rewrites? > > Eienne > Neither of the two, you were asking about mounting in a sub-uri in the previous posts, that requires some kind of ruling. For mounting under / (or empty SCRIPT_NAME to be more compliant with WSGI) youby roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> On Sat, Aug 05, 2017 at 11:47:24AM -0400, Etienne Robillard wrote: > > Hi there, > >> The workaround suggested below is not working. > > From the words here, it is not clear to me what specific configuration > you are using. > >> The only case where >> Django correctly handle uWSGI transport is when PATH_INFO is set to >> DOCUMENT_URI in uwsgi_paraby roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> Hi Roberto, > > Le 2017-07-27 à 13:45, Roberto De Ioris a écrit : >> >> by using something like this (in the config, tune the regexps as >> required): >> >> >> route = ^/(.+?)/(.+)$ setscriptname:/$1 >> route = ^/(.+?)/(.+)$ setpathinfo:/$2 >> > I use a dynamic regex URL resolver to resolve a request URI to a > callback function.by roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> Hi Roberto, > > That is not effective. My app uses PATH_INFO to resolve a URL (ie: > /blog/create/) to a callback function. > > Could it be possible to just use : > > uwsgi_param PATH_INFO $path_info > > Assuming $path_info is the request_uri minus the location... > > E > Nope, as already said there is no way to manage this directly in nginx (and technicalby roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> Hi all, > > Le 2017-07-27 à 11:25, Francis Daly a écrit : >> On Thu, Jul 27, 2017 at 07:45:28AM -0400, Etienne Robillard wrote: >> >> Hi there, >> >>> I'm not sure I understand the logic of this. Can someone please >>> explain why the variable PATH_INFO is set to $document_uri in >>> uwsgi_params? >> My guess (without knowing thby roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> Hi Roberto, > > > Le 2017-07-27 à 09:52, Roberto De Ioris a écrit : >> >>> Hi again, this is not what manage-script-name is for. It is a >>> uWSGI-specific option for when you only PATH_INFO and you want to >>> generate >>> SCRIPT_NAME accordingly. This requires to "mount" apps under specific >>> paths. > Ok. I reallyby roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> Hi Roberto, > > I use gevent-fastcgi for production. I wish to have the time to dive in > the internals of uWSGI to understand how PATH_INFO and SCRIPT_NAME gets > rewritten by uWSGI. I believe the implementation of --manage-script-name > is incorrect and should be fixed to support having a empty or not set > SCRIPT_NAME value. > > Etienne Hi again, this is not whatby roberto - Nginx Mailing List - English
Re: Problem with uWSGI and PATH_INFO - 6 years ago
> Hi Roberto, > > My Django app runs perfectly ok under FastCGI and nginx but is not > capable of resolving the proper PATH_INFO under uWSGI. In > fastcgi_params, the value of PATH_INFO and SCRIPT_NAME are set to > "$fastcgi_script_name". My nginx config looks like this: > > location / { > > uwsgi_pass django; > > include uwsgi_params; > > } &gby roberto - Nginx Mailing List - English
Re:Re: Re: Need Help about useing Nginx with UWSGI - 8 years ago
> Debug on test environment. If I can not access an URI of my app, Then I > can try to access uwsgi server port directly to get rid of the possibility > that my nginx configuration problem. But UWSGI processes can only start > as one protocol server, and I can not find any plugin for browsers that > support the uwsgi protocol. So I would like to deploy the app on test > enviby roberto - Nginx Mailing List - English
vpn-ws a VPN over websockets (behind nginx) - 9 years ago
Hi all, i have released a tool for building VPNs (with various operational modes) using only websockets as a transport. The server-side delegates all the authentication, authorization and proxy part to nginx: https://github.com/unbit/vpn-ws i hope it will be useful Regards -- Roberto De Ioris http://unbit.com _______________________________________________ nginx mailing list nginx@nginx.orgby roberto - Nginx Mailing List - English
Re: uwsgi problems - 9 years ago
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/09/2014 12:49 PM, Greg Barker wrote: >> Option #2 should work, here's what I have for my uwsgi site. >> Double check your permissions on the directory the uwsgi.sock lives >> in. >> >> My nginx conf: location / { uwsgi_pass >> unix:///var/www/my_app/my_virtualenv/run/uwsgi.sock; include >by roberto - Nginx Mailing List - English
Re: CGI support - Sorry to bring it up - 9 years ago
> Hi All, > We've built a new EC2 server based on Virtualmin + Nginx. I've seen > Nginx recommended a lot over the years so thought if we are moving to > the cloud, and want things to be optimal, then it's time to give it a > go. Before our setup has been Virtualmin + Apache (with suexec and fcgid). > > For some of our old Perl CGI scripts we've hit the issue I'm sure mostby roberto - Nginx Mailing List - English
Re: SlowFS Cache or Proxy_Cache for GridFS - 9 years ago
> Elena, > would you please share your experiences with us? it's been 3 ears and now > we > (a small startup) want to create a production solution that can scale. > > Mongo still didn't release asynchronous driver and we want to go down > nginx+nodejs script for gridfs (nginx-gridfs proejct also no longer > supported). > > I'd love to hear from you if possible, Youby roberto - Nginx Mailing List - English
Re: Nginx-Clojure Module Release 0.1.0--Let Nginx embrace Clojure & Java - 9 years ago
> Thanks for your good hints. > > I see there 's a good no-blocking mysql client Libdrizzle from > https://launchpad.net/drizzle. > > With Nginx-lua or Openresty , Libdrizzle has been used in production. yes, both can be of great inspiration for you/your project > > I won't hope every thing is no-blocking and I think it is unnecessary. > unfortunataley (well, todayby roberto - Nginx Mailing List - English
Re: Nginx-Clojure Module Release 0.1.0--Let Nginx embrace Clojure & Java - 9 years ago
> roberto Wrote: > ------------------------------------------------------- >> >> Sorry, but are you saying that your suggested usage for concurrency is >> multiprocessing ? >> >> Multiprocessing is completely alien in the jvm (the vm is not even >> fork-friendly) and that would mean the nginx worker completly give >> control >> to the jvm and tby roberto - Nginx Mailing List - English
Re: Nginx-Clojure Module Release 0.1.0--Let Nginx embrace Clojure & Java - 9 years ago
> With the default setting pipe is not used. > > Pipe is only used for enable jvm thread pool mode only when jvm_workers > > 0 > (jvm_workers default = 0). > > Further more pipe is never used to transfer the while request or response > message. > When under jvm thread pool mode, pipe is only used to transfer a event > flag > (only one pointer size)。 > >by roberto - Nginx Mailing List - English
Re: Nginx-Clojure Module Release 0.1.0--Let Nginx embrace Clojure & Java - 9 years ago
> May be somebody wonder what the differences between Nginx UWsig Module > and > Nginx Clojure Module when integrating JVM. > > They are quite different. Nginx Clojure Module embed JVM instance into the > Nginx Worker and they are in the same process and have the same memory > address space. > > There 's no IPC cost when using Nginx Clojure Module and even no thread &by roberto - Nginx Mailing List - English
Re: Hiring a dev: nginx+interchange - 9 years ago
> Hello, I use a perl framework called interchange (icdevgroup.org) and > I've been using a perl module called Interchange::Link to interface > interchange to apache: > > https://github.com/interchange/interchange/blob/master/dist/src/mod_perl2/Interchange/Link.pm > > I'd like to switch from apache to nginx and I need to hire someone to > help me interface interchange to ngby roberto - Nginx Mailing List - English
Re: [PATCH v2] uwsgi over ssl - 10 years ago
> Hello! > > On Tue, Nov 19, 2013 at 11:24:50AM +0100, Roberto De Ioris wrote: > >> Hi, this is a new patch for uwsgi over ssl support aimed at nginx 1.5.x >> >> It now exposes 4 options: >> >> uwsgi_ssl >> >> uwsgi_ssl_session_reuse >> >> uwsgi_ssl_protocols >> >> uwsgi_ssl_ciphers > > Sorry for long delay. I'veby roberto - Nginx Development
[PATCH v2] uwsgi over ssl - 10 years ago
Hi, this is a new patch for uwsgi over ssl support aimed at nginx 1.5.x It now exposes 4 options: uwsgi_ssl uwsgi_ssl_session_reuse uwsgi_ssl_protocols uwsgi_ssl_ciphers Regards -- Roberto De Ioris http://unbit.it_______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-develby roberto - Nginx Development
Re: [PATCH] ssl support for uwsgi upstream - 10 years ago
> Hello! > > On Mon, Nov 18, 2013 at 02:31:13PM +0100, Roberto De Ioris wrote: > >> >> > Hello! >> > >> > On Sun, Nov 17, 2013 at 08:50:14AM +0100, Roberto De Ioris wrote: >> > >> >> Hi all, attached you will find a patch adding two new options to the >> >> uwsgi >> >> upstream module: >> >> >&by roberto - Nginx Development
Re: [PATCH] ssl support for uwsgi upstream - 10 years ago
> Hello! > > On Sun, Nov 17, 2013 at 08:50:14AM +0100, Roberto De Ioris wrote: > >> Hi all, attached you will find a patch adding two new options to the >> uwsgi >> upstream module: >> >> uwsgi_ssl <flag> (default off) >> >> uwsgi_ssl_session_reuse <flag> >> >> uwsgi over ssl has been officially added today to the uWSGIby roberto - Nginx Development
[PATCH] ssl support for uwsgi upstream - 10 years ago
Hi all, attached you will find a patch adding two new options to the uwsgi upstream module: uwsgi_ssl <flag> (default off) uwsgi_ssl_session_reuse <flag> uwsgi over ssl has been officially added today to the uWSGI project (1.9.20) It has been a requirement of a single customer so i do not know how much real uses it has, but being a very tiny (and non invasive) patch i think it willby roberto - Nginx Development
[semi-OT] GridFS uWSGI plugin - 10 years ago
Hi everyone, latest uWSGI release got GridFS support: https://uwsgi-docs.readthedocs.org/en/latest/GridFS.html In my company we are using it behind nginx for serving items from a replica set https://uwsgi-docs.readthedocs.org/en/latest/GridFS.html#combining-with-nginx Currently the plugin misses "range" support and mongodb authentication, but they will be added in the next releases.by roberto - Nginx Mailing List - English
Re: uWSGI + Moin (subdir) + Nginx - 10 years ago
> Hi, > > I followed the example in: > > http://projects.unbit.it/uwsgi/wiki/Example#MoinMoinonlinenow > > > However when I type domain/wiki I get a message that the page does not > exist yet... which already tells me something is wrong, and also all my > URL's are point to '/' not '/wiki' > > I can't seem to figure out why this happens... I tough using: > &gby roberto - Nginx Mailing List - English
Re: [PATCH] websockets support for uwsgi protocol - 10 years ago
> > Ok, so the next question is: any specific reason to exclude normal > CGI responses with "Status" as in your patch? > > I in fact don't like the idea of supporting http-like answers with > status like from CGI-like protocols, correct way is to use > "Status" header. Not sure why Manlio introduced it at all, > probably due to some compatibility concerby roberto - Nginx Development
Re: [PATCH] websockets support for uwsgi protocol - 10 years ago
> >> Hello! >> >> (Cc'd nginx-devel@ as this is better list for this discussion.) >> >> On Wed, Feb 20, 2013 at 02:30:38PM +0100, Roberto De Ioris wrote: >> >>> Hi, the (tiny) attached patch enable support for new websockets >>> handling >>> when the uwsgi protocol is used instead of HTTP. >>> >>> I have tested itby roberto - Nginx Mailing List - English
Re: [PATCH] websockets support for uwsgi protocol - 10 years ago
> >> Hello! >> >> (Cc'd nginx-devel@ as this is better list for this discussion.) >> >> On Wed, Feb 20, 2013 at 02:30:38PM +0100, Roberto De Ioris wrote: >> >>> Hi, the (tiny) attached patch enable support for new websockets >>> handling >>> when the uwsgi protocol is used instead of HTTP. >>> >>> I have tested itby roberto - Nginx Development
Re: [PATCH] websockets support for uwsgi protocol - 10 years ago
> Hello! > > (Cc'd nginx-devel@ as this is better list for this discussion.) > > On Wed, Feb 20, 2013 at 02:30:38PM +0100, Roberto De Ioris wrote: > >> Hi, the (tiny) attached patch enable support for new websockets handling >> when the uwsgi protocol is used instead of HTTP. >> >> I have tested it with various websocket libraries and with the api >>by roberto - Nginx Development
Re: [PATCH] websockets support for uwsgi protocol - 10 years ago
> Hello! > > (Cc'd nginx-devel@ as this is better list for this discussion.) > > On Wed, Feb 20, 2013 at 02:30:38PM +0100, Roberto De Ioris wrote: > >> Hi, the (tiny) attached patch enable support for new websockets handling >> when the uwsgi protocol is used instead of HTTP. >> >> I have tested it with various websocket libraries and with the api >>by roberto - Nginx Mailing List - English
 |
 |
 |
 |
|