Custom client can't receive anything after the first reply

[iXo]

Hi,
I know this is nearly a dead library, but it allow me to code a quick and dirty test client.

And I seems to have a strange problem : after having recieived and processed a reply to the first options method, the socket recvfrom will receive nothing and will fire a timeout error.

Could you help me to solve this problem ?

[turboladen]

@iXo did you figure out your issue?

[iXo]

Yes, my bad, it was on the server side that the message wasn't sent.

Just for information : I am using netty, the rtspencoder shipped with netty store an internal state to know if a complet message have been sent or not. If it wasn't the case an exception if fired and catched silently.

The problem is in fact that there are 2 type of messages : header only and full http request / response. If a not full is sent (I was using a not full response for the options response) the state is set to wait for a body. And if you sens after that a not full response the is invalid to send it. Changed everything to full http response and everything works well.

Sorry for this false report.

[turboladen]

@iXo no problem! I know how that goes.