Hello, I have a following problem with Nginx. Here is the scenario.
There is a client app that sends request to Nginx Proxy with following
parameter. The parameter is already url encoded.
GET /X/Y/Z.aspx?id=abc%3D%3D
Now, I noticed that Nginx applies url encode to % and make it as %25 when it
red
As Francis stated, you need to look for the mainline version, not the
stable version. They have different repositories.
http://nginx.org/packages/mainline/centos/6/x86_64/RPMS/
On Thu, Jul 27, 2017 at 12:47 PM, Gee Bunny wrote:
> There might be talk of binaries being available on the page you l
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):
[uwsgi]
route = ^/(.+?)/(.+)$ setscriptname:/$1
route = ^/(.+?)/(.+)$ setpathinfo:/$2
I use a dynamic regex URL resolver to resolve a request URI to a
cal
There might be talk of binaries being available on the page you
linked, but if you check the repo link I provided (to the NGINX hosted
YUM Repository for CentOS 6 x86_64) there's no version 1.13 it goes as
high as nginx-1.12.1 only.
Don't take my word for it, see for yourself:
http://nginx.org/pa
> 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
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
Le 2017-07-27 à 12:47, Roberto De Ioris a
> 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_param
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 kno
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 the history):
The uwsgi_params values are an e
> 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
>>
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 really don
> 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 empt
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
See the 'upstream_EBLB_with_IWCP.txt' document and the pdf documentation,
the primary control (ie. signaling) should be (initiated) triggered by your
edge controllers or router.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,275671,275688#msg-275688
___
> 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 / {
>
> uws
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
Thanks
But what about the next part when actually we are in production and if there
is need for change of secret Key on Nginx.
" Is there a way to implement the token authentication with two secret key
i.e primary and secondary
So that If the first one did not work, then try the second one.
Th
Hi, uWSGI apparently does some weird voodoo tricks to manage SCRIPT_NAME
and PATH_INFO when using nginx: "The WSGI standard dictates that
|SCRIPT_NAME| is the variable used to select a specific application.
Unfortunately u nginx is not able to rewrite PATH_INFO accordingly to
SCRIPT_NAME. For s
Your backend is returning a HTTP 500, which likely indicates a PHP Fatal
Error. You should check the error log for the site.
On Thu, Jul 27, 2017 at 10:28 AM, emios wrote:
> I bought a new VPS and I try to transfer my working ZendApp (work in
> previous hosting with DirectAdmin). Now i install n
Hello!
On Thu, Jul 27, 2017 at 03:55:40AM -0400, foxgab wrote:
> i want to change the redirect location URI protocol to https if that is
> using, so i tried to configure like this:
>
> proxy_redirect ~*^http://$host(/.*)?$ $scheme://$host$1;
>
> but that didn't work, so i change it to:
>
Like i said before
c0nw0nk Wrote:
---
> Update your web application for example (PHP) first then how ever many
> hours later when all caches for your web application have cleared
> restart your Nginx so it only accepts secure links.
Update your
Hello!
On Sat, Jul 22, 2017 at 11:10:02AM -0400, mohini wrote:
> I have an working nginx module (http_content_Modify_module) that acts as a
> proxy and manipulates some specific http data coming to the proxy before
> sending it to the upstream server.Used nginx1.6.2 for this and was
> implemented
I bought a new VPS and I try to transfer my working ZendApp (work in
previous hosting with DirectAdmin). Now i install nginx with php5 and mysql
i this is my php configuration - works well
http://178.216.200.85/info.php
I turn on display errors in php.ini and it shows me error in writable
/_cache
i want to change the redirect location URI protocol to https if that is
using, so i tried to configure like this:
proxy_redirect ~*^http://$host(/.*)?$ $scheme://$host$1;
but that didn't work, so i change it to:
proxy_redirect http://$http_host $scheme://$http_host;
then, it works
24 matches
Mail list logo
