I have a gateway node that has turned on digest authorization and I'm having problems retrieving a file from the nodes web server now. I have run the configure script to create wget with the --enable-digest option. I was expecting to see the Basic authorization used initially (as seen below) but that a 401 error would be returned instead of a 403. From reading the RFC I was under the impression that the node would return a 401 error with the parameters needed to encrypt the password (realm, some key, etc).
I'm hoping there is a simple explaination as to why this is not working. I have tried to run curl to the same node and it does perform the negotiation correctly. Are there known issues with wget and digest?
Steve Glymph
Nortel Networks
[EMAIL PROTECTED]
> ./wget --http-user=Admin --http-passwd=Admin -d -v http://47.142.134.127/FS/BOARD.ini
DEBUG output created by Wget 1.9.1 on solaris2.8.
--10:09:36-- http://47.142.134.127/FS/BOARD.ini
=> `BOARD.ini.1'
Connecting to 47.142.134.127:80... connected.
Created socket 3.
Releasing 560c0 (new refcount 0).
Deleting unused 560c0.
---request begin---
GET /FS/BOARD.ini HTTP/1.0
User-Agent: Wget/1.9.1
Host: 47.142.134.127
Accept: */*
Connection: Keep-Alive
Authorization: Basic QWRtaW46QWRtaW4=
---request end---
HTTP request sent, awaiting response... HTTP/1.1 403 Forbidden
Content-Type: text/html
Server: Allegro-Software-RomPager/3.10
Closing fd 3
10:09:36 ERROR 403: Forbidden.
