Hello, igorclark
Perhahs you can create a shell to launch nginx, and before that, ejecute a
shell to assign a environment variable as a result of the execution of a
program, or create (update) a file that is to be included from nginx config
file when starting
Some ideas:
http://nginx.2469901.n2.
Hi all,
I want to read some remote values via HTTP into nginx config variables, just
once at nginx startup / reload time, and pass them as fastcgi_params into
PHP scripts. I control the remote system, so I'll know if it needs to
re-read and can send a HUP to nginx. I don't need it to happen every
Hello!
On Wed, Sep 03, 2014 at 10:10:01AM -0400, erankor2 wrote:
> Maxim, thank you very much for your response.
>
> To clarify - the problem is not about freeing the request (I don't think
> there's a resource leak here), the problem is that the connection is just
> left hanging until the clien
On Thursday 04 September 2014 02:04:09 Valentin V. Bartenev wrote:
> On Wednesday 03 September 2014 23:50:07 georg wrote:
> > Hi Valentin,
> >
> > Thanks for your help.
> >
> > On 09/03/2014 10:23 PM, Valentin V. Bartenev wrote:
> > > On Wednesday 03 September 2014 20:18:50 georg wrote:
> > > [..
On Wednesday 03 September 2014 23:50:07 georg wrote:
> Hi Valentin,
>
> Thanks for your help.
>
> On 09/03/2014 10:23 PM, Valentin V. Bartenev wrote:
> > On Wednesday 03 September 2014 20:18:50 georg wrote:
> > [..]
> >> However, using Iceweasel 31.0-1~bpo70+1 (out of wheezy-backports), the
> >>
Hi Valentin,
Thanks for your help.
On 09/03/2014 10:23 PM, Valentin V. Bartenev wrote:
> On Wednesday 03 September 2014 20:18:50 georg wrote:
> [..]
>> However, using Iceweasel 31.0-1~bpo70+1 (out of wheezy-backports), the
>> browser console reads various 403 forbidden, and the nginx log is
>> te
Could it be that Apache 2.2 + mod_fastcgi + PHP FPM logs IP addresses
to errror.log
but NGINX + PHP-FPM does not?
I mean not to a log file specified in error_log configuration option.
[03-Sep-2014 19:37:24 UTC] {message from e.g. error_log()}
*no IP address in the the line
After commenting
On Wednesday 03 September 2014 20:18:50 georg wrote:
[..]
> However, using Iceweasel 31.0-1~bpo70+1 (out of wheezy-backports), the
> browser console reads various 403 forbidden, and the nginx log is
> telling me the cause: "[...] 25108#0: *200 access forbidden by rule,
> client: XX.XX.XX.XX, server
[Not sure if this is the right list, because I'm uncertain if the
following is intended behaviour or a problem in nginx or the involved
browsers. So would be happy if you guys could me give some advice and a
pointer in case, this mail should better be directed elsewhere; if so,
sorry for the noise.
Hello everyone.
I am using a rewrite similar to below
location /home {
rewrite ^/(.*) https://mysite.com/homepage/?next=/redirectionurl
redirect;
}
The issue is that nginx is not encoding the URL before it redirects.
So this is failing at the server that is receiving this request
On Wed, Sep 3, 2014 at 5:13 PM, Grozdan wrote:
> On Wed, Sep 3, 2014 at 5:07 PM, Steve Wilson
> wrote:
>> I've just thought of another angle for this. Is this hitting your
>> default/only site? If it's got a host header you could create a site just
>> for that that bins all requests off with a 4
On Wed, Sep 3, 2014 at 5:07 PM, Steve Wilson wrote:
> I've just thought of another angle for this. Is this hitting your
> default/only site? If it's got a host header you could create a site just
> for that that bins all requests off with a 444 and no logging.
Yes, it's the only site. I will try
I've just thought of another angle for this. Is this hitting your
default/only site? If it's got a host header you could create a site
just for that that bins all requests off with a 444 and no logging.
On 02/09/2014 12:08, Grozdan wrote:
Hi,
Somehow my server gets hit by torrent requests whi
On 02/09/2014 17:38, Grozdan wrote:
On Tue, Sep 2, 2014 at 3:09 PM, Maxim Dounin
wrote:
Hello!
On Tue, Sep 02, 2014 at 12:17:12PM +0100, Steve Wilson wrote:
Torrent clients have their own user agent normally, I had a need a
while
back to block some which we used the magic 444 to kill it.
i
Maxim, thank you very much for your response.
To clarify - the problem is not about freeing the request (I don't think
there's a resource leak here), the problem is that the connection is just
left hanging until the client closes it / the server is restarted.
It is true that write_event_handler g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have a page contains 'http://' assets, and I do redirect on my nginx
like this :
- BEGIN CONFIGURATION
server {
listen 80;
server_name subdomain.domain.com;
return 301 https://$http_host$request_uri$
OK thanks Maxim. I will check your recommendation and will let you know.
--Manish
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252379,253036#msg-253036
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
17 matches
Mail list logo
