On Wed, Jan 18, 2017 at 10:52 PM, Daniel wrote:
> Hi there,
>
> i wanted to try something like a Wildcard DocRoot:
>
>
> server {
> listen 80;
> root /var/www/branches/*/current/web/;
> server_name auto.deploy.fcse.int;
>
I use this:
server {
listen
On Wednesday, 24 August 2016, Amanat wrote:
> i was using Apache from last 3 years. never faced a single problem. Few
> days
> ago i think to try Nginx. As i heard from mny people. Its very fast memory
> efficient webserver. Trust me guys. Nginx can never be memory efficient.
>
Usually when peop
On 26 May 2016 at 14:04, Dimka wrote:
> Face the same problem, empty $ssl_session_id variable.
>
> If ssl_session_ticket off, $ssl_session_id always contain ID.
>
> How can I identify client connection if no ssl session id available?
>
I would also know answer for this. It is kinda either:
1. se
On Tuesday, 8 March 2016, Krishna Kumar K K wrote:
> I am able to modify the set-cookie header from the server to flag it
> secure. I am trying to do the same in the request header as well.
>
Those flags are instructions to client. They don't have meaning on request
headers. Only on response hea
On 7 March 2016 at 22:15, kris...@brocade.com
wrote:
>
> Could you tell me more about LUA or some links where i can read about it?
>
Here you go:
https://github.com/openresty/lua-nginx-module#header_filter_by_lua
There you can replace the Set-Cookie-headers, and append HttpOnly and
Secure flags.
On Tuesday, 29 December 2015, Maxim Dounin wrote:
> Hello!
>
> On Tue, Dec 29, 2015 at 05:07:37PM +0800, 天河石 - 谢金鹏 wrote:
>
> > I like to add the following entry:
> >
> >
> > http://www.google-analytics.com/ga.js";>
> >
> >
> > in section. How do I do it?
>
> Assuming you want to do it usin
On 29 December 2015 at 11:07, 天河石 - 谢金鹏 <2305958...@qq.com> wrote:
> I like to add the following entry:
>
> http://www.google-analytics.com/ga.js";>
>
>
> in section. How do I do it?
>
Okay, I will do it for you:
http://www.google-analytics.com/ga.js";>
If you later need to remove
> On 30 September 2015 at 02:20, Valentin V. Bartenev
wrote:
> The code was already broken, it was a coincidence that it worked.
I can now confirm that fixing code fixed the issue. Thank you. HTTP/2 works
like a charm!
___
nginx mailing list
nginx@nginx
On 30 September 2015 at 02:20, Valentin V. Bartenev wrote:
> The code was already broken, it was a coincidence that it worked.
Thanks for the patience. Case closed. I just wanted to be sure. It seems
like Chrome is more demanding on HTTP/2 headers than others.
Regards
Aapo
__
On 29 September 2015 at 13:38, Sergey Kandaurov wrote:
> So, the header field name output as generated with php
> (and previously guessed by Valentin),
> is invalid as per 7230, which is in turn referenced in 7540.
>
> : field-name = token
> : token = 1*tchar
> : tchar = "!" / "#" / "quot; /
On 29 September 2015 at 12:25, Francis Daly wrote:
> On Tue, Sep 29, 2015 at 01:06:50AM +0300, Aapo Talvensaari wrote:
> > It just sets the status code. It is normal PHP 5.3 code [1]. I might
need
> > to compile nginx by hand to get more debug info.
>
> For what it's wor
On 29 September 2015 at 01:06, Aapo Talvensaari
wrote:
> On 29 September 2015 at 00:01, Valentin V. Bartenev
wrote:
>> What does ":" mean in the header() function?
>> If it returns ":" as a header, then it's the cause of the error.
>>
> It just se
On 29 September 2015 at 00:01, Valentin V. Bartenev wrote:
> >On Monday 28 September 2015 20:59:23 Aapo Talvensaari wrote:
> >> On 28 September 2015 at 19:44, Valentin V. Bartenev
> wrote:
> >> If Ajax request sends a PUT request with XmlHttt
On 28 September 2015 at 19:44, Valentin V. Bartenev wrote:
> On Wednesday 23 September 2015 06:28:37 Aapo Talvensaari wrote:
> >> I did get errors like:
> >> net::ERR_SPDY_COMPRESSION_ERROR
> > Could you provide a debug log with problematic request?
>
I tried to d
On 23 September 2015 at 11:48, itpp2012 wrote:
> Have you seen this one
> http://forum.nginx.org/read.php?29,261735,261737#msg-261737
> Have you completely removed the spdy module ?
I have seen that, but I'm using the official Ubuntu precise packages from
nginx.org, so I kinda think it should be
I tried the 1.9.5 release with http2 and it worked fine, but Ajax request
especially were problematic.
I did get errors like:
net::ERR_SPDY_COMPRESSION_ERROR
And the status code was 0. With the former spdy support I didn't have any
problems. I'm also using fastcgi and PHP5 in this server where I
16 matches
Mail list logo
