Closed Freekers closed 4 months ago
@Freekers I am not sure if that is related to chunked encoding. I tested the same setup in a development build of zoraxy with no chunk encoding & connected via local IP address, it still not works. See here for more discussion related to proxmox and zoraxy. I will keep this open for now.
@Freekers I am not sure if that is related to chunked encoding. I tested the same setup in a development build of zoraxy with no chunk encoding & connected via local IP address, it still not works. See here for more discussion related to proxmox and zoraxy. I will keep this open for now.
I think it maybe Websocket support?
Proxmox compatibility mode is now added in v3.1.0. Zoraxy will automatically force legacy HTTP connection, rewrite chunk encoding settings and perform a few more compatibility stuffs if PVE cookie is detected in the request.
Is your feature request related to a problem? Please describe. Yes, currently I receive an HTTP Error 501 when trying to use the VM console in Proxmox, while being reverse proxied via Zoraxy. According to this thread on the Proxmox forums, this might be due to Chunked Encoding being enabled.
Describe the solution you'd like Option/Toggle to Disable Chunked Encoding, preferably per HTTP Proxy host.
Describe alternatives you've considered
Additional context