Paw-Issues
Paw-Issues copied to clipboard
luckymarmot
Paw HTTP Library refuses to connect to Play! routes
Play! and Paw seem to hate each other, and I'm not too sure why. :(
I'm in the process of experimenting with Play! while getting comfortable with Scala. To that end, I've set up a pretty simple 'hello world' style API with an endpoint or two that just logs a simple message and returns a 200 OK to the caller with the same message.
Both valid, and invalid API endpoints served by Play! are completely inaccessible vie Paw when using the default HTTP connection library. It appears as though the connection is immediately closed, as there is no HTTP status code, the response body is 0 bytes, and the error tab of the response interface simply says 'Socket closed by remote peer'. The server console doesn't log anything, which leads me to think that it never actually recieves the request from Paw.
I am able to get expected responses when browsing to the endpoint via Chrome, or calling out to the endpoint via curl/wget. Additionally, swapping the connection library used (under Preferences > HTTP > HTTP Library) from Paw HTTP Library to either of the other two default ones causes everything to behave as expected.
Unfortunately I haven't poked into Paw debugging too much, but I suppose that'd be the next step from me if this isn't enough to go on.
Some version data: Paw version: 2.3.1 (Retail) Play! Version: 2.4.2 Scala version: 2.11.7
It's definitely not a blocker as the other two seem to be doing everything one would expect. :)
@Sunspar just dropping you a line to say thanks for the info and that we aren't forgetting about this! I done myself a few experiments with our HTTP library, and it seems like things are a little weird. I have worked on a fix, making the code better and more reliable.
Do you still have this issue now? Is it happening all the time? Still happening after you restart the app?
Would you mind giving a quick try to the previous version of Paw to see if that's any better/worse?
Otherwise, I'll have a fix for thew few glitches that I've found ready early this week… thanks!
@Sunspar we still couldn't reproduce this issue, but we have fixed many things from the HTTP library in the latest version... https://luckymarmot.com/paw/updates/2.3.3 does it fix the issue? thanks!
@Sunspar Have you been able to reproduce this recently? The latest version of Paw is 3.0.8.
Hi, I also have this problem with paw 3.1.10
GET http://localhost:9000/ throw an error "Socket closed by remote peer".
but curl "http://localhost:9000/" works fine in terminal
