WARP in proxy only mode doesn't handle 301 http response code

I am using Cloudflare Warp clien on Windows, proxy only mode.
If I try to open a “redirect” URL, then I get error message in the browser about EMPTY_RESPONSE.

See for example:
http://facebook.hu ← it should redirect to facebook.com. But with WARP proxy id doesn’t redirect, but get the browser an empty response.

(Windows 11 latest patch, Warp Client latest 2023.07.x, but problem found in the 2023 April version.)

Does anybody use this feature, or only me?

This URL doesn’t work too:

ERR_CONNECTION_RESET

Maybe, I am the only one person who wanted to use this feature? Nobody else?

Auto http->https redirect doen’t work too, for example: http://as.hu/ip It should redirect to https://as.hu/ip , but instead of the redirect ERR_EMPTY_RESPONSE in Chrome.

I hope, somebody read it from the developer team.

Is there any plan to fix this issue?

I am using Cloudflare Warp clien on Windows, proxy only mode.
If I try to open a “redirect” URL, then I get error message in the browser about EMPTY_RESPONSE.

See for example:
http://facebook.hu ← it should redirect to facebook.com. But with WARP proxy id doesn’t redirect, but get the browser an empty response.

Auto http->https redirect doen’t work too, for example: http://as.hu/ip It should redirect to https://as.hu/ip , but instead of the redirect ERR_EMPTY_RESPONSE in Chrome.

This doesn’t work too: Undocumented 8086 instructions, explained by the microcode ( ERR_CONNECTION_RESET )

(Windows 11 latest patch, Warp Client latest 2023.07.x, but problem found in the 2023 April version too.)

I hope, it will be fixed in the next version. But at least, some answer from the developers would be nice.

Any news?

Maybe some fix?

Did you already submit a bug :wbug: report to the engineers through the client?

Yes, without any reaction in the last 2 months.

Do not close, before any solution, please.