It's a server (or proxy) problem! 
Use a sniffer such as Wireshark if you don't believe it.     

After a long delay (timeout?) the server answers
with a 404, and closes the connection.

Arno Garrels

Fastream Technologies wrote:
> Hello,
> Could you guys try this url and the below actions with your own
> httptst's? 
> - (returns 404 which is ok)
> - head
> - get
> - head (second head stalls) This occurs both when you do it
> programmatically and by hand! Please help!
> Best Regards,
> SZ
To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to