[erlang-bugs] http:request/5 returning wrong request and crashing

Vincent de Phily vincent.dephily@REDACTED
Fri Jun 12 15:22:26 CEST 2009


On Friday 12 June 2009 15:10:03 Micael Karlberg wrote:
> The crash is easy to fix, but the root cause (for the
> crash) is unknown. As to the very strange order of the
> replies, I have no idea yet (try running with a longer
> timeout).
>
> I have put up an improved version here:
>
> http://www.erlang.org/~bmk/download//otp8052/inets-5.1.1-OTP8052-P01.tgz
>
> I have added some trace features. Add the following
> call before starting inets:
>
> 	inets:enable_trace(max, io).
>
> For example in the escript code:
>
> main(_Args) ->
>      Profile = myprofile,
>      inets:enable_trace(max, io),
>      ok = inets:start(),
>      {ok, _ProfilePid} = inets:start(httpc, [{profile, Profile}]),
>      loop(Profile).
>
> This should give us some more info.

Thanks, I will try that.

For what it's worth, I'm currently working around the bug with
http:set_options([{cookies, enabled}, {max_keep_alive_length, 0}], ProfilePid)

Also, this workaround only seem to work with 13B01, it doesn't help with 13B.


-- 
Vincent de Phily
Mobile Devices
+33 (0) 666 301 306
+33 (0) 142 119 325

Warning
This message (and any associated files) is intended only for the use of its
intended recipient and may contain information that is confidential, subject
to copyright or constitutes a trade secret. If you are not the intended
recipient you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message, is
strictly prohibited. If you have received this message in error, please
notify us immediately by replying to the message and deleting it from your
computer. Any views or opinions presented are solely those of the author
vincent.dephily@REDACTED and do not necessarily represent those of 
the
company. Although the company has taken reasonable precautions to ensure no
viruses are present in this email, the company cannot accept responsibility
for any loss or damage arising from the use of this email or attachments.


More information about the erlang-bugs mailing list