I am using wget to retrieve a webpage but getting error like:

$ wget https://abc.com/plsql/test.abc
--06:20:36--  https://abc.com/plsql/test.abc
=> `test.abc'
Resolving abc.com... done.
Connecting to abc.com[xxx.xx.xxx.xx]:443... connected.
HTTP request sent, awaiting response...
End of file while parsing headers.
Retrying.

--06:21:07--  https://abc.com/plsql/test.abc
(try: 2) => `test.abc'

I am puzzled as I am able to hit the browser to get required page in
proper format. Any inputs/suggestions where I am going wrong?

Thanks in advance.

[ Post a follow-up to this message ]

"Yogi" <yogeshkagrawal@gmail.com> writes:

> I am using wget to retrieve a webpage but getting error like:
>
> $ wget https://abc.com/plsql/test.abc
> --06:20:36--  https://abc.com/plsql/test.abc
>            => `test.abc'
> Resolving abc.com... done.
> Connecting to abc.com[xxx.xx.xxx.xx]:443... connected.
> HTTP request sent, awaiting response...
> End of file while parsing headers.
> Retrying.
>
> --06:21:07--  https://abc.com/plsql/test.abc
>   (try: 2) => `test.abc'
>
> I am puzzled as I am able to hit the browser to get required page in
> proper format. Any inputs/suggestions where I am going wrong?

Is this a public URL?  If it is, and you posted it, someone could
perhaps have a look.

--
Måns Rullgård
mru@inprovide.com

[ Post a follow-up to this message ]

This is not a public URL. I have changed it for posting on this group.
Actual URL is something different from what i have given but gist is
same.

[ Post a follow-up to this message ]

On Wed, 26 Oct 2005 06:45:19 -0700, Yogi wrote:

> I am using wget to retrieve a webpage but getting error like:
>
> $ wget https://abc.com/plsql/test.abc
> --06:20:36--  https://abc.com/plsql/test.abc
>            => `test.abc'
> Resolving abc.com... done.
> Connecting to abc.com[xxx.xx.xxx.xx]:443... connected.
> HTTP request sent, awaiting response...
> End of file while parsing headers.
> Retrying.
>
> --06:21:07--  https://abc.com/plsql/test.abc
>   (try: 2) => `test.abc'
>
> I am puzzled as I am able to hit the browser to get required page in
> proper format. Any inputs/suggestions where I am going wrong?

Browsers accept a lot of crap that isn't HTTP, use something to get a
dump of what the request/response is ... that'll probably tell you.

--
James Antill -- james@and.org
http://www.and.org/and-httpd

[ Post a follow-up to this message ]

Thanks James for your response. Are you referring to request/response
from web browser? Any pointers how to get dump of same?
thanks in advance.

[ Post a follow-up to this message ]

yogeshkagrawal@gmail.com wrote...
> Thanks James for your response. Are you referring to request/response
> from web browser? Any pointers how to get dump of same?
> thanks in advance.

Easiest way is to use Ethereal to capture the dialog between a
browser and the server along that same URL, then highlight one of the
packets of the conversation, right click your mouse, and select
'follow TCP stream'.  It'll extract the packet data and present it to
you for direct examination.

Load that into your text editor of choice and have at it.

http://www.ethereal.com

[ Post a follow-up to this message ]

entropy wrote:
> yogeshkagrawal@gmail.com wrote... 
>
> Easiest way is to use Ethereal ...

Actually the easiest way (IMHO) is to install either ieHTTPHeaders
(http://www.blunck.info/iehttpheaders.html) for IE and/or
LiveHTTPHeaders (http://livehttpheaders.mozdev.org/) for Firefox. These
will let you make a normal browser connection and then review the exact
set of headers which were passed. Of course Ethereal will do the same
thing but it's lower-level and a bit harder to learn.

HT

[ Post a follow-up to this message ]

henry.townsend@not.here wrote...
> entropy wrote: 
>
> Actually the easiest way (IMHO) is to install either ieHTTPHeaders
> (http://www.blunck.info/iehttpheaders.html) for IE and/or
> LiveHTTPHeaders (http://livehttpheaders.mozdev.org/) for Firefox. These
> will let you make a normal browser connection and then review the exact
> set of headers which were passed. Of course Ethereal will do the same
> thing but it's lower-level and a bit harder to learn.

Heck, I'd never even heard of this before.  Thanks.

[ Post a follow-up to this message ]

In article <MPG.1dca75dc8429900b98a5d6@news.verizon.net>, entropy <entropy@domain.invalid> w
rites:
> yogeshkagrawal@gmail.com wrote... 
>
> Easiest way is to use Ethereal to capture the dialog between a
> browser and the server along that same URL, then highlight one of the
> packets of the conversation, right click your mouse, and select
> 'follow TCP stream'.  It'll extract the packet data and present it to
> you for direct examination.

In this case the OP is making an HTTPS request, so Ethereal won't be
of much help (unless his server's negotiating a null cipher suite,
which is unlikely).

If the problem isn't reproducible over an unencrypted channel, he'll
need to use some other mechanism.  Henry Townsend's suggestion of
ieHTTPHeaders - I haven't tried that tool, so I don't know if it
works with HTTPS, but as a plug-in it ought to have access to the
plaintext.  (Looks like a useful tool, in any case.)

--
Michael Wojcik                  michael.wojcik@microfocus.com

Thanks for your prompt reply and thanks for your invitatin to your
paradise.  Based on Buddihism transmigration, I realize you, European,
might be a philanthropist in previous life!  -- supplied by Stacy Vickers

[ Post a follow-up to this message ]

>> Easiest way is to use Ethereal to capture the dialog between a 
>
>In this case the OP is making an HTTPS request, so Ethereal won't be
>of much help (unless his server's negotiating a null cipher suite,
>which is unlikely).

One way to do this is with telnet to the http port, and manually type
in the request.  Run it with a pipe to tee(1) or under script(1) to
get a log of the session.  For a https request, use
openssl s_client -connect host:port
(sorta "secure telnet") in place of telnet.  It also has piles of
other options for user certs and stuff.  If something's getting
messed up in setting up the secure connection, debug options here
may help.

Gordon L. Burditt

[ Post a follow-up to this message ]