[erlang-questions] inets - http:request with invalid host ip(Sanjaya Vitharana)

Sanjaya Vitharana sanjaya@REDACTED
Tue May 29 12:00:33 CEST 2007


Erlang Release R11B-4 with inets-4.7.11

Also for the same url "links" gives the similler result. I mean it hangs for
a long time & gives below output. Also I tried with traceroute, it also
takes a long time to compete the below output.

Since all these tools takes long time, can't this be any related to any
network configuration (NAT or something ) ?

Also where documented "etimedout" ??

If you need further infomation I can provide you with traces. Please guide
me about the traces you need

Thanks

Sanjaya Vitharana

[root@REDACTED erlang]# links -source
"http://202.124.160.149/src/cf/1414/cricket/scoreline_odi/menu.php?key=1&ses
sion=a02857230011801002496201&ch=58&serverid=1"
ERROR at dump.c:188: Receive timeout

[root@REDACTED erlang]#

4>

Last login: Mon May 28 15:20:21 2007 from 202.124.181.34
[root@REDACTED ~]# traceroute 202.124.160.149
traceroute to 202.124.160.149 (202.124.160.149), 30 hops max, 38 byte
packets
 1  202.124.160.37 (202.124.160.37)  1.119 ms  1.287 ms  1.097 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
[root@REDACTED ~]#




----- Original Message -----
From: "Ingela Anderton Andin" <ingela@REDACTED>
To: <erlang-questions@REDACTED>
Sent: Tuesday, 29 May 2007 02:48 pm
Subject: Re: [erlang-questions] inets - http:request with invalid host
ip(Sanjaya Vitharana)


>
> > Hi,
> >
> > Of cource I put an ip which is not visible (and url also not there).
> >
> > 2> test:test_url().
> >
URL="http://202.124.160.149/src/cf/1414/cricket/scoreline_odi/menu.php?key=1
&session=a02857230011801002496201&ch=58&serverid=1"
> >  Time for Synchronous request 189028171 microseconds
ResSync={error,etimedout}
> >  Time for Asynchronous request 188972235 microseconds ResASync={ok,
> >
#Ref<0.0.0.119>}
> >
> > Check the above results for time taken to execute http:request. (test
code attached)
> >
> > 1.) It has taken a large amount of time to execute both requests
> > 2.) And time difference to exit from Synchronous and Asynchronous
request are approximately same.
> >
> > Is this OK ???
> >
> > What I am thinking is the time taken to perform Asynchronous request as
not acceptable. Am I wrong ?
> > If the IP is not visible (or not available) Why such long time taken to
give ANY result ?
> >
> > Is this a bug ?
> >
> Which version of inets are you using? I just tried your URL and for a
> synchronous request
> I got {ok,{{"HTTP/1.1",503,"Service Unavailable"}, ...  after some time
> and the asynchronous
> version almost immediately  returned  {ok, #Ref<0.0.0.97>} as expected.
>
> Regards Ingela - OTP team
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>





More information about the erlang-questions mailing list