What is the maximum amount of the buffer? I could not locate any
documentation on any of this with regards to how it would cause an error on
SPDY.
And doesn't "FIXME" indicate this is a bug? Why would it be in the code
otherwise?
I already removed SPDY and the errors went away, as did the probl
Hi Francis,
On 05/30/2013 12:37 AM, Francis Daly wrote:
On Wed, May 29, 2013 at 04:35:03PM +0200, Patrick Lists wrote:
Hi there,
[snip]
What does
curl -I https:///doc/postfix-2.6.6/README_FILES/AAAREADME
show as the Content-Type?
If it is "text/plain", your nginx is doing what you told
On Wed, May 29, 2013 at 04:35:03PM +0200, Patrick Lists wrote:
Hi there,
> This works fine when I browse to for example:
> https:///doc/procmail-3.22/examples/1procmailrc
>
> But it does not work for:
>
> https:///doc/postfix-2.6.6/README_FILES/AAAREADME
>
> Not work meaning Firefox offers the
Hello!
On Tue, May 28, 2013 at 01:32:48PM -0400, B.R. wrote:
> Hello Maxim,
>
> I spent a lot of time trying to figure out what is happening.
> It seems that after some service restart, the problem sometimes disappear
> before coming back again on the following try.
>
> I finally managed to cap
On 05/29/2013 06:11 PM, wishmaster wrote:
[snip]
What is in log?
In the access.log:
Working ok when browsing a procmail file:
- - [29/May/2013:18:15:15 +0200] "GET
/doc/procmail-3.22/examples/ HTTP/1.1" 200 1597
"https:///doc/procmail-3.22/" "Mozilla/5.0 (X11; Linux x86_64;
rv:21.0) Gec
--- Original message ---
From: "Patrick Lists"
Date: 29 May 2013, 17:35:18
> Hi,
>
> On a CentOS 6.4 box with nginx 1.4.1 I would like to expose
> /usr/share/doc/* as /doc so I can easily browse the docs from
> the installed packages.
>
> Config I have right now (thanks Nodex on irc for
Hi,
On a CentOS 6.4 box with nginx 1.4.1 I would like to expose
/usr/share/doc/* as /doc so I can easily browse the docs from
the installed packages.
Config I have right now (thanks Nodex on irc for pointing me to types):
# docs
location /doc {
alias /usr/share/doc/;
autoindex on;
type
On Wednesday 29 May 2013 09:03:41 Mike wrote:
[...]
>
> 2013/05/29 00:22:53 [alert] 25981#0: *8781732 FIXME: chain too big in spdy
> filter: 25516336 while sending to client, client: x.x.x.x, server: x.y.z,
> request: "GET /attachments/113914 HTTP/1.1", upstream:
> "fastcgi://127.0.0.1:9001", host
Hi
I thought HEAD should behave as GET only in case of success
after reading the RFC I understand it's should be the same on any response
Thanks
On Wed, May 29, 2013 at 3:10 PM, Maxim Dounin wrote:
> Hello!
>
> On Wed, May 29, 2013 at 02:49:46PM +0300, Hagai Avrahami wrote:
>
> > Hi
> >
> > I a
Hello!
On Wed, May 29, 2013 at 02:49:46PM +0300, Hagai Avrahami wrote:
> Hi
>
> I am trying to configure Nginx to deny HTTP HEAD requests
>
> 1. By adding the following to configuration file
>
> if ($request_method !~ ^(GET)$) {
> return 405;
> }
>
> 2. Explicitly in the module
>
> if (!
Hi
I am trying to configure Nginx to deny HTTP HEAD requests
1. By adding the following to configuration file
if ($request_method !~ ^(GET)$) {
return 405;
}
2. Explicitly in the module
if (!(r->method & (NGX_HTTP_GET))) {
return NGX_HTTP_NOT_ALLOWED;
}
Nginx returns 405 status c
11 matches
Mail list logo
