Edwin Madari wrote:
>Hi,
>
>I need to receive http document(s) from outside the fire wall, through a
>proxy server which requires userid and password combination.
So, it is your proxy server that needs the userid and password?
You may need to implement cookie caching in your script. This is
particularly necessary if it is the distant remote server that needs the
userid and password. The cookies carry the context for subsequent URL
requests.
>
>Currently in Netscape, when I type any address outside our intranet, I get
>the password prompt dialog window. After user id and password is provided,
>my current and all subsequent URL requests are honored.
Why not use Netscape to open the door and then use your script to fetch the
documents from outside the firewall. This should work if your agent name
is the same as your browser name and if the proxy does not use cookies.
>
>With the documentation from LWP, I am able to retrieve documents from our
>intranet using both lwp-request and using a simple perl script. I am unable
>to go out to the internet. Web client programming book from Oreilly is out
>of print.
Clifford Wong's book. A great book - I was also surprised that O'Reilly
let it go out of print.
A method for proceeding:
Set up a libwww script to accept headers and bodies from Netscape and
forward them on through the firewall (bidirectional too). You could
arrange to have this script write out the conversations to a file.
Looking at this file of headers and bodies would enable you to change your
current script so that it would send the userid and password correctly to
the firewall.
(this means that the conversation snoop script would have to be in a
cgi-bin directory which would be accessible by a webserver.
I hope this helps.
BobG
