Suggest looking at gitlab:
https://about.gitlab.com/downloads/
It works well with Nginx and meets most needs for version control. If you
stick with the standard bundle and plugins then your upgrade management for
gitlab will remain clean and simple.
IMHO
On 31 Oct 2015 16:40, "Francis Daly" wro
Yes, thanks. Packet level debugging would be the next step. Just thought
someone on the list may have run into this hard limit before.
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi Maxim,
Yes, did that before posting to the list and no error 414 is logged. I
have not come across this before and hence the question to the list. Based
on the lack of anything logged it does look to be a hard limit being
reached in the browser, but again, I thought that I would post to the l
Hi Maxim,
The logs (even with debug enabled) do not produce any evidence to isolate
this to the browser hitting a maximum count. However, on the other hand
there is no evidence of large_client_header_buffers being reached either.
Any other thought on isolating the issue beyond changing the GET t
large_client_header_buffers directive is accepted, but ignored
nginx version: nginx/1.0.14
We are trying to pass a file through nginx but it dies at the same line
level no matter what changes we make to nginx.conf or if we adjust the
server block in the vhost as indicated in
http://nginx.2469901.n
