Nginx redirection problem in odoo

Hi all: I'm trying to print a report with product ean13 barcodes and the barcodes are printed blank. I think my problem is an incorrect redirection problem because I can see correctly the barcodes if I browse to the url:

3rd party modules requiring ngx_http_postpone_filter_module

Hello, I'm currently looking for ideas to resolve a 3rd party module regression[1][2] that I keep running into, and figured it would be best to consult the experts. The ngx_http_postpone_filter_module is a critical helper for many modules to ensure subrequests are properly ordered. But I can't

Re: Advise for NTLM-Auth

Andreas, Kerberos and NTLM are two completely different ways of authenticating a user. Whilst they essentially do the same thing, the main difference that you care about is that Kerberos works correctly over HTTP, unlike NTLM which does not. - which module you may suggest There are a number of

Re: Advise for NTLM-Auth

Max Clements: Depending on the versions of Windows and what you are trying to do, it may be possible to use Kerberos via Nginx, rather than NTLM. that's what I mean saying "I don't care if it's named NTLM or ugly_voodoo" You name it "Kerberos" - fine. Now I came up with two questions: -

Re: Advise for NTLM-Auth

Depending on the versions of Windows and what you are trying to do, it may be possible to use Kerberos via Nginx, rather than NTLM. It requires some foo setting up Service Principal Names, but does work properly via an HTTP proxy, and provides passthrough auth, which seems to be what the desire

Re: (52) Empty reply from server

On Tue, Apr 19, 2016 at 03:51:17PM +0530, Pankaj Chaudhary wrote: Hi there, > i am trying to search for one header with the specified name > > i am not able to get header value . https://www.nginx.com/resources/wiki/start/topics/examples/headers_management/ lists four ways to try this. You are

Re: Fix for ngx_unlock() and thus race conditions in AIO mechanism

Hello! On Tue, Apr 19, 2016 at 05:09:55PM +0100, Mindaugas Rasiukevicius wrote: > Maxim Dounin wrote: > > Patch that follows the same logic as used in ngx_update_time(), that is, > > with an explicit ngx_memory_barrier() call before ngx_unlock(), and no > > barrier semantics

nginx-1.9.15

Changes with nginx 1.9.1519 Apr 2016 *) Bugfix: "recv() failed" errors might occur when using HHVM as a FastCGI server. *) Bugfix: when using HTTP/2 and the "limit_req" or "auth_request" directives a timeout or a "client violated flow

nginx-1.9.15

Изменения в nginx 1.9.15 19.04.2016 *) Исправление: при использовании HHVM в качестве FastCGI-сервера могли возникать ошибки "recv() failed". *) Исправление: при использовании HTTP/2 и директив limit_req или auth_request при чтении

Re: Fix for ngx_unlock() and thus race conditions in AIO mechanism

Maxim Dounin wrote: > Patch that follows the same logic as used in ngx_update_time(), that is, > with an explicit ngx_memory_barrier() call before ngx_unlock(), and no > barrier semantics in ngx_unlock() itself: I can just point out that pretty much all spin-lock

[nginx] nginx-1.9.15-RELEASE

details: http://hg.nginx.org/nginx/rev/13070ecfda67 branches: changeset: 6521:13070ecfda67 user: Maxim Dounin date: Tue Apr 19 19:02:37 2016 +0300 description: nginx-1.9.15-RELEASE diffstat: docs/xml/nginx/changes.xml | 55

[nginx] release-1.9.15 tag

details: http://hg.nginx.org/nginx/rev/5b5a2d8d4d97 branches: changeset: 6522:5b5a2d8d4d97 user: Maxim Dounin date: Tue Apr 19 19:02:37 2016 +0300 description: release-1.9.15 tag diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diffs

Re: reuseport в конфигах nginx

Всем добрый день, Вас не смущает, что при этом часть соединений будет потеряна? Ну это не супер приятно да, но альтернатива хуже. Потому что в альтернативном варинте часть соединений будет невозможна на то время, пока мы опустили один контейнер, а потом подняли второй. Но я лишь о том,

[nginx] HTTP/2: send the output queue after emitting WINDOW_UPDATE.

details: http://hg.nginx.org/nginx/rev/9070ba416284 branches: changeset: 6520:9070ba416284 user: Valentin Bartenev date: Tue Apr 19 17:38:49 2016 +0300 description: HTTP/2: send the output queue after emitting WINDOW_UPDATE. The WINDOW_UPDATE frame could be left in

[nginx] HTTP/2: skip data frames in case of internal errors.

details: http://hg.nginx.org/nginx/rev/9ac934dd5dd8 branches: changeset: 6519:9ac934dd5dd8 user: Valentin Bartenev date: Tue Apr 19 17:38:49 2016 +0300 description: HTTP/2: skip data frames in case of internal errors. This prevents possible processing of such

[nginx] HTTP/2: don't send WINDOW_UPDATE for an empty request body.

details: http://hg.nginx.org/nginx/rev/7760b54d5458 branches: changeset: 6518:7760b54d5458 user: Valentin Bartenev date: Tue Apr 19 17:38:49 2016 +0300 description: HTTP/2: don't send WINDOW_UPDATE for an empty request body. Particularly this prevents sending

[nginx] Thread pools: memory barriers in task completion notifications.

details: http://hg.nginx.org/nginx/rev/657e029bac28 branches: changeset: 6517:657e029bac28 user: Maxim Dounin date: Tue Apr 19 17:18:28 2016 +0300 description: Thread pools: memory barriers in task completion notifications. The ngx_thread_pool_done object isn't

[nginx] HTTP/2: write logs when refusing streams with data.

details: http://hg.nginx.org/nginx/rev/ab16126a06a0 branches: changeset: 6516:ab16126a06a0 user: Maxim Dounin date: Mon Apr 18 21:18:24 2016 +0300 description: HTTP/2: write logs when refusing streams with data. Refusing streams is known to be incorrectly

Re: Fix for ngx_unlock() and thus race conditions in AIO mechanism

Hello! On Mon, Apr 18, 2016 at 10:40:59PM +0100, Mindaugas Rasiukevicius wrote: > Some background: enabling AIO threads can result in "stuck" connections, > permanently waiting for handler callback (in the system these connections > appear in a CLOSE_WAIT state). This happens due to race

Re: Slice cache

Maxim Dounin Wrote: --- > Hello! > > On Tue, Apr 19, 2016 at 03:24:37AM -0400, S.A.N wrote: > > > > По умолчанию range-запросы из кеша работают только в том случае, > > > если в ответе бекенда был заголовок Accept-Ranges и должна быть > > >

Re: Slice cache

Hello! On Tue, Apr 19, 2016 at 03:24:37AM -0400, S.A.N wrote: > > По умолчанию range-запросы из кеша работают только в том случае, > > если в ответе бекенда был заголовок Accept-Ranges и должна быть > > явно указана длина ответа. > > Супер, спасибо, отдали Accept-Ranges все работает. > >

Re: (52) Empty reply from server

Hi all, i am trying to search for one header with the specified name i am not able to get header value . below my code snippet. ngx_http_core_main_conf_t *clcf; ngx_str_t *type; ngx_uint_t hash; ngx_str_tval = ngx_string("http_cookie"); clcf =

Re: Slice cache

> По умолчанию range-запросы из кеша работают только в том случае, > если в ответе бекенда был заголовок Accept-Ranges и должна быть > явно указана длина ответа. Супер, спасибо, отдали Accept-Ranges все работает. Кстати есть ли смысл бекенду сжимать (gzip) свой ответ, если клиенты запрашивают

Re: Advise for NTLM-Auth

Hi. Am 18-04-2016 22:59, schrieb A. Schulze: Maxim Dounin: Just a side note: NTLM auth is broken by design and violates HTTP basic rules. Avoid using it if you can. to be clear: I don't care if it's named NTLM or ugly_voodoo The goal is a nginx accesses by a IE/edge browser. Users should

Nginx ssl

Добрый день Есть сервер nginx работает как обратный прокси сервер, для некоторого количества сайтов, один из них нужно перевести на https, конфиг server { server_name www.example.com example.com; location / { proxy_pass http://192.168.0.23; proxy_redirect http://localhost/