| strange behaviour of SOCKET [message #62038] |
Wed, 20 August 2008 14:48  |
pgrigis
Messages: 436
Registered: September 2007
|
Senior Member |
|
|
Hi folks,
for some mysterious reasons, socket is not working anymore
for me. I can access files in my own internet domain (i.e.
harvard.edu)
but I cannot access files [i.e. readf on the unit given by socket
hangs]
outside that domain (using HTTP GET commands).
I tried spawn, 'wget ...' from the same command line and this can get
files from everywhere.
Notice that "socket" itself and printf,unit both work (or at least
do not give troubles), is only readf,unit that hangs.
So the question is: how is socket different than wget?
If this is a firewall issue, what settings are causing this?
I know this is not much information to go on, but this issue
seems pretty hard to track down, so I just though I could ask
here before trying more desperate measures...
Ciao,
Paolo
|
|
|
|
| Re: strange behaviour of SOCKET [message #62109 is a reply to message #62038] |
Fri, 22 August 2008 06:45  |
pgrigis
Messages: 436
Registered: September 2007
|
Senior Member |
|
|
pgri...@gmail.com wrote:
> Yes,
>
> I was using higher level routines such as sock_copy and webget,
> and after some debugging I found out (not surprisingly) that socket
> was the culprit.
>
> Actually I found out that I can get the files if I want
read wait ;-)
> a long time
> (I haven't timed it, but it is more then several tens of minutes).
>
> I am in contact with my sysadmins to find out whether this comes
> from interaction with our web-filtering.
>
> Ciao,
> Paolo
>
> Pedro.Rodriguez.Pasc...@gmail.com wrote:
>> Hello,
>>
>> The problem might be related to HTTP1.0/HTTP1.1 protocols in the
>> socket connection. Unfortunately, I am not an expert in internet
>> protocols nor in IDL, but I found similar problems that were solved by
>> using the latest version of webget.pro function in the astrolib
>> library by Wayne Landsman.
>>
>> I apologize if this post is actually non-sense.
>>
>> Pedro
|
|
|
|
| Re: strange behaviour of SOCKET [message #62110 is a reply to message #62038] |
Fri, 22 August 2008 06:38 |
pgrigis
Messages: 436
Registered: September 2007
|
Senior Member |
|
|
Yes,
I was using higher level routines such as sock_copy and webget,
and after some debugging I found out (not surprisingly) that socket
was the culprit.
Actually I found out that I can get the files if I want a long time
(I haven't timed it, but it is more then several tens of minutes).
I am in contact with my sysadmins to find out whether this comes
from interaction with our web-filtering.
Ciao,
Paolo
Pedro.Rodriguez.Pasc...@gmail.com wrote:
> Hello,
>
> The problem might be related to HTTP1.0/HTTP1.1 protocols in the
> socket connection. Unfortunately, I am not an expert in internet
> protocols nor in IDL, but I found similar problems that were solved by
> using the latest version of webget.pro function in the astrolib
> library by Wayne Landsman.
>
> I apologize if this post is actually non-sense.
>
> Pedro
|
|
|
|
|
|
| Re: strange behaviour of SOCKET [message #62112 is a reply to message #62038] |
Fri, 22 August 2008 05:43 |
Pedro.Rodriguez.Pascu
Messages: 3
Registered: September 2007
|
Junior Member |
|
|
Hello,
The problem might be related to HTTP1.0/HTTP1.1 protocols in the
socket connection. Unfortunately, I am not an expert in internet
protocols nor in IDL, but I found similar problems that were solved by
using the latest version of webget.pro function in the astrolib
library by Wayne Landsman.
I apologize if this post is actually non-sense.
Pedro
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
