401 error using username/password for site

[karlkindt4]

I have used CSE HTML Validator from verison 6.5 up through 9. I did not upgrade to 12 until last week. Through versions 6.5 up to 9 I had no issue with using the program to log in to validate HTML on a site that requires a user name and password; I teach HTML/XHTML programming, so the students have to upload files via FTP, which is where I need to see/validate their files (from the Web, not local).

Anyway, I have never had any issue until 12. When I try to do what I have always done in every past version 6.5 through 9, I get a 401 error. I never got that before. I even re-installed 9, did everything I did with 12, and 9 works just fine still! The in-app browser works (the one that uses IE), but that is not satisfactory. I need to be able to hit the site directly like I did with the old versions.

I have uninstalled all versions of HTML Validator then re-installed clean. It doesn't matter. The old 9 works. The new 12 does not. I get the 401 every time with exactly the same settings I use in 9 (which works) in 12 (which does not work).

HELP!

[Albert Wiersch]

Hello,

I'm sorry for the trouble. I will look into this tomorrow and report back. It sounds like it could be a bug with the username/password handling in v12.

[karlkindt4]

To help you bug-hunt this, here is something weird I forgot to mention in my original post: I used the beta of 12 for a couple of months, and it worked fine! I used beta 12 from about the time it was released until late December, and it worked just fine where the full 12 will not! I hope this helps!

[Albert Wiersch]

To help you bug-hunt this, here is something weird I forgot to mention in my original post: I used the beta of 12 for a couple of months, and it worked fine! I used beta 12 from about the time it was released until late December, and it worked just fine where the full 12 will not! I hope this helps!

Strange. Perhaps it has something to do with using HTTP/1.1 instead of HTTP/1.0 which is a change I made that I think was made about the time that you are saying it stopped working.

This could mean your server "doesn't like" HTTP/1.1. What web server and version are you using?

Can you copy and paste in a reply the "Open Progress" text from a failed URL download attempt? The client/server communication may shed some light on what's going on.

Thanks.

[karlkindt4]

I am just the professor teaching an HTML course at a university. I am not sure what web server and version we have, but it does appear from the open progress text that is a Microsoft product being used.

Here is the open progress text from a failed URL download attempt:

Proxy> No proxy being used
Command> GET /daniellefuller37/skills.htm HTTP/1.1
Command> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Command> Connection: close
Command> User-Agent: CSE HTML Validator Professional (http://www.htmlvalidator.com/)
Command> Host: labwebs.webster.edu
Command>
Header> HTTP/1.1 401 Unauthorized
Header> Content-Length: 1656
Header> Content-Type: text/html
Header> Server: Microsoft-IIS/6.0
Header> WWW-Authenticate: Negotiate
Header> WWW-Authenticate: NTLM
Header> WWW-Authenticate: Basic realm="labwebs.webster.edu"
Header> MicrosoftOfficeWebServer: 5.0_Pub
Header> X-Powered-By: ASP.NET
Header> Date: Tue, 08 Jan 2013 23:24:47 GMT
Header> Connection: close
Command> GET /daniellefuller37/skills.htm HTTP/1.1
Command> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Command> Connection: close
Command> User-Agent: CSE HTML Validator Professional (http://www.htmlvalidator.com/)
Command> Host: labwebs.webster.edu
Command> Authorization: NTLM TlRMTVNTUAABAAAAB4IAAAAAAAAgAAAAAAAAACAAAAA=
Command>
Header> HTTP/1.1 401 Unauthorized
Header> Content-Length: 1539
Header> Content-Type: text/html
Header> Server: Microsoft-IIS/6.0
Header> WWW-Authenticate: NTLM TlRMTVNTUAACAAAAFAAUADgAAAAFgoICw67TnC9PtoQAAAAAAAAAAGQAZABMAAAABQLODgAAAA9TAFYAUgBXAEUAQgBHADAAMwAxAAIAFABTAFYAUgBXAEUAQgBHADAAMwAxAAEAFABTAFYAUgBXAEUAQgBHADAAMwAxAAQAFABzAHYAcgB3AGUAYgBnADAAMwAxAAMAFABzAHYAcgB3AGUAYgBnADAAMwAxAAAAAAA=
Header> MicrosoftOfficeWebServer: 5.0_Pub
Header> X-Powered-By: ASP.NET
Header> Date: Tue, 08 Jan 2013 23:24:47 GMT
Header> Connection: close
Command> GET /daniellefuller37/skills.htm HTTP/1.1
Command> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Command> Connection: close
Command> User-Agent: CSE HTML Validator Professional (http://www.htmlvalidator.com/)
Command> Host: labwebs.webster.edu
Command> Authorization: NTLM TlRMTVNTUAADAAAAGAAYAF4AAAAYABgAdgAAAAAAAABAAAAADgAOAEAAAAAQABAATgAAAAAAAACOAAAABYIAAGsAaQBuAGQAdABpAHYAQQB0AGwAYQBuAHQAaQBzAPaW55qwQQhBpqBfUo5SKiQ+EllXK25J1X76TJlr/zzy/st8Y5M81A+0chF8ivcHMw==
Command>
Header> HTTP/1.1 401 Unauthorized
Header> Content-Length: 1539
Header> Content-Type: text/html
Header> Server: Microsoft-IIS/6.0
Header> WWW-Authenticate: Negotiate
Header> WWW-Authenticate: NTLM
Header> WWW-Authenticate: Basic realm="labwebs.webster.edu"
Header> MicrosoftOfficeWebServer: 5.0_Pub
Header> X-Powered-By: ASP.NET
Header> Date: Tue, 08 Jan 2013 23:24:47 GMT
Header> Connection: close

-- Request Done --
StatusCode = 401
ReasonPhrase = Unauthorized

[Albert Wiersch]

Thanks... sorry, I should have also asked earlier, can you post the same from a version of CSE HTML Validator that works? Then I can compare the difference.

[karlkindt4]

Here is what version 9 does (and works):

Proxy> No proxy being used
Command> GET /daniellefuller37/skills.htm HTTP/1.0
Command> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Command> User-Agent: CSE HTML Validator Professional (http://www.htmlvalidator.com/)
Command> Host: labwebs.webster.edu
Command>
Header> HTTP/1.1 401 Unauthorized
Header> Content-Length: 1656
Header> Content-Type: text/html
Header> Server: Microsoft-IIS/6.0
Header> WWW-Authenticate: Negotiate
Header> WWW-Authenticate: NTLM
Header> WWW-Authenticate: Basic realm="labwebs.webster.edu"
Header> MicrosoftOfficeWebServer: 5.0_Pub
Header> X-Powered-By: ASP.NET
Header> Date: Wed, 09 Jan 2013 01:03:02 GMT
Header> Connection: close
Command> GET /daniellefuller37/skills.htm HTTP/1.0
Command> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Command> Connection: Keep-alive
Command> User-Agent: CSE HTML Validator Professional (http://www.htmlvalidator.com/)
Command> Host: labwebs.webster.edu
Command> Authorization: NTLM TlRMTVNTUAABAAAAB4IAAAAAAAAAAAAAAAAAAAAAAAA=
Command>
Header> HTTP/1.1 401 Unauthorized
Header> Content-Length: 1539
Header> Content-Type: text/html
Header> Server: Microsoft-IIS/6.0
Header> WWW-Authenticate: NTLM TlRMTVNTUAACAAAAFAAUADgAAAAFgoICYrRAb86tKu4AAAAAAAAAAGQAZABMAAAABQLODgAAAA9TAFYAUgBXAEUAQgBHADAAMwAxAAIAFABTAFYAUgBXAEUAQgBHADAAMwAxAAEAFABTAFYAUgBXAEUAQgBHADAAMwAxAAQAFABzAHYAcgB3AGUAYgBnADAAMwAxAAMAFABzAHYAcgB3AGUAYgBnADAAMwAxAAAAAAA=
Header> MicrosoftOfficeWebServer: 5.0_Pub
Header> X-Powered-By: ASP.NET
Header> Date: Wed, 09 Jan 2013 01:03:02 GMT
Header> Connection: keep-alive
Command> GET /daniellefuller37/skills.htm HTTP/1.0
Command> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Command> Connection: Keep-alive
Command> User-Agent: CSE HTML Validator Professional (http://www.htmlvalidator.com/)
Command> Host: labwebs.webster.edu
Command> Authorization: NTLM TlRMTVNTUAADAAAAGAAYAF4AAAAYABgAdgAAAAAAAABAAAAADgAOAEAAAAAQABAATgAAAAAAAAAAAAAABYIAAGsAaQBuAGQAdABpAHYAQQB0AGwAYQBuAHQAaQBzAMTyYQvySJmGA3Ee1ncAVHJXAgGkeAKN7SRaUWKP5fFxksit6A6J6L7b3DNXyAHlqQ==
Command>
Header> HTTP/1.1 200 OK
Header> Content-Length: 653
Header> Content-Type: text/html
Header> Last-Modified: Sat, 05 Feb 2011 06:34:33 GMT
Header> Accept-Ranges: bytes
Header> ETag: "825937c0fec4cb1:1993"
Header> Server: Microsoft-IIS/6.0
Header> MicrosoftOfficeWebServer: 5.0_Pub
Header> X-Powered-By: ASP.NET
Header> Date: Wed, 09 Jan 2013 01:03:02 GMT
Header> Connection: keep-alive

StatusCode = 200
ReasonPhrase = OK

[Albert Wiersch]

The major difference I see right away is the HTTP/1.1 vs HTTP/1.0 request.

I will be sending you a link to a new version to download and try. It adds an option to use HTTP/1.0 instead of HTTP/1.1. Please try this version, uncheck the "HTTP/1.1" option in the Open from the Web dialog (so that HTTP/1.0 is used), and let me know if it makes any difference.

Thanks!

UPDATE: Sent via private message through the forum.

[karlkindt4]

It works! That did it! Thank you! Is there somewhere I can save that option (to use HTTP/1.0 not 1.1) so I don't have to un-check that box every time? I use this many, many times every week and would love to not have to un-check the box each time.

[Albert Wiersch]

It works! That did it! Thank you! Is there somewhere I can save that option (to use HTTP/1.0 not 1.1) so I don't have to un-check that box every time? I use this many, many times every week and would love to not have to un-check the box each time.

Great! I'm glad that fixed it, though I'm not exactly sure why.

The version you have will always default to HTTP/1.1 but I'll look into either remembering that setting or having an option to default to HTTP/1.0 instead, and try to get you another update tomorrow.

[Albert Wiersch]

It works! That did it! Thank you! Is there somewhere I can save that option (to use HTTP/1.0 not 1.1) so I don't have to un-check that box every time? I use this many, many times every week and would love to not have to un-check the box each time.

Hello,

I've PM'd you a new download link.

In the 'Options' menu in the Open From the Web dialog, there should be a new option - 'Default to HTTP/1.1'. Make sure that option is unchecked and then it should not default to HTTP/1.1 any more.

[Albert Wiersch]

Hello,

If you're still around on this thread, could you tell me if there is any proxy involved anywhere in this request? And if so, what type of proxy authentication? It was suggested to me that it could be an issue with an old proxy and lack of HTTP/1.1 support. I suppose it could also be an old or problematic web server. It looks like you're using IIS v6 which I think is about 10 years old now, so I wonder if it could be related to that.

If you're using HTTPS, perhaps it is related to this:
HTTP 1.1 host headers are not supported when you use SSL