(no this is not a dupe of #141 - that issue is about *responses)* :smile:
I've got an (embedded) client that streams an HTTP 1.1 POST payload by using Transfer-Encoding: chunked. Since normally it would be POSTing data to a cloud service, using xip.io + pow is incredibly handy to configure the device to send data to my dev server.
Unfortunately when I run pow (in proxy mode) the request appears to be dropped and never makes it to my app. I can see the request hit my host in wireshark, and the request appears in the pow access.log but nothing on my app server. But if I stop pow and have my app listen directly on port 20559 it works. So I presume pow/nack is dropping the request. Wireshark doesn't show any response at all, actually.
I also verified the request contains the correct Host header for pow to forward the request (e.g. myapp.192.168.1.5.xip.io) which works correctly from the browser.
(no this is not a dupe of #141 - that issue is about *responses)* :smile:
I've got an (embedded) client that streams an HTTP 1.1 POST payload by using
Transfer-Encoding: chunked. Since normally it would be POSTing data to a cloud service, using xip.io + pow is incredibly handy to configure the device to send data to my dev server.Unfortunately when I run pow (in proxy mode) the request appears to be dropped and never makes it to my app. I can see the request hit my host in wireshark, and the request appears in the pow access.log but nothing on my app server. But if I stop pow and have my app listen directly on port 20559 it works. So I presume pow/nack is dropping the request. Wireshark doesn't show any response at all, actually.
I also verified the request contains the correct
Hostheader for pow to forward the request (e.g.myapp.192.168.1.5.xip.io) which works correctly from the browser.