DIVA- nginx issue #98

New Issue

DSRLIN · 2024-01-30T06:56:27Z

DSRLIN commented

2024-01-30 06:56:27 +00:00

Nowadays nginx follows the RFC standard that force server to respond 400 when they receive an abnormal header and don't care whether the http request's version is 1.1 or not.
see: https://github.com/nginx/nginx/blob/master/src/http/ngx_http_request.c#L2145

Project Diva sends requests without host header, so if using nginx in production environment, this will cause issues.
Maybe in production environment users could use other proxies instead, like haproxy. This reverse proxy can forcely rewrite requests' header including host.

Nowadays nginx follows the RFC standard that force server to respond 400 when they receive an abnormal header and don't care whether the http request's version is 1.1 or not. see: https://github.com/nginx/nginx/blob/master/src/http/ngx_http_request.c#L2145 Project Diva sends requests without host header, so if using nginx in production environment, this will cause issues. Maybe in production environment users could use other proxies instead, like haproxy. This reverse proxy can forcely rewrite requests' header including host.

Midorica commented

2024-01-30 13:21:03 +00:00

Not too sure what you are reporting as an issue since i have tested on a cabinet and it was connecting just fine even under nginx

Mind giving a bit more details on what issue you have faced?

Here is some logs from my last gameplay which did use nginx:

Not too sure what you are reporting as an issue since i have tested on a cabinet and it was connecting just fine even under nginx Mind giving a bit more details on what issue you have faced? Here is some logs from my last gameplay which did use nginx: ![image](/attachments/9dbd12c8-79ab-472e-ac01-00ef351bc939)

image.png

12 KiB

DSRLIN closed this issue

2024-02-04 01:03:57 +00:00

Sign in to join this conversation.