Re: WinCE Web Server Auth Not working
- From: "John Spaith [MS]" <jspaith@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 31 Oct 2007 09:36:10 -0700
Chris - it turns out that the .Net Framework HTTP parsing stuff did not like
the format that the web server was sending 401 responses back in. (Tech
details are we were calling one send() for the HTTP header and another
send() for the actualy "access-denied" body and it didn't like that.) My
apologies that you had to hit this since it's MS stuff on both sides.
You have a few options, you'll have to chose which is the best (or maybe
least bad?)
* CE 6.0 fixed this issue, though I understand going from CE5->6 is a
non-trivial undertaking.
* On the .Net framework that shipped with VS 2003 (.Net 1 or something I
think, I'm really a native guy) it did not have this issue on not liking
CE's response, so if you can "link" against that you should be OK. It's the
VS 2005 latest+greatest .Net that hit this.
(http://groups.google.com/group/microsoft.public.windowsce.embedded/browse_thread/thread/1270892027ee6c21/73b1e904559c7620?lnk=st&q=%22The+server+committed+a+protocol%22+spaith#73b1e904559c7620
has exact product names.)
* You can request a QFE for CE 5.0 to fix this issue.
http://support.microsoft.com/ I know there's always the concern on getting
charged for making support requests, though there's no charge if it's an MS
bug, so feel free to use my name confirming this is the case. I can't make
guarantees, since there is the .Net workaround on using 03 framework they
may not be able to back-port the fix, but you can try at least.
I've brought this to .Net team's attention but don't believe they have fixed
this in any newer .Net (or if it was it was fixed without being marked as
such), so unfortunately upgrading on .Net isn't an option.
Once again very sorry you hit this.
--
John Spaith
Senior Software Design Engineer
Windows CE Networking
Microsoft Corporation
http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2007 Microsoft Corporation. All rights
reserved.
"fuzz_ball" <chris.r.putman@xxxxxxxxx> wrote in message
news:1193444797.606693.186460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
So I have a WinCE device running the web server in order to expose a
web service to a COM object on the CE device. Everything works great
if authorization is off ("A" = 0). The problem is, we want to have
authorization turned on, so I did ("A" = 1).
Now I keep getting, as reported in the web server log, 401 -
Unauthorized. On the client side (a .NET desktop application) I get a
real unhelpful error message "The server committed a protocol
violation. Section=ResponseStatusLine <IP Addresss>" Where "IP
Address" is the IP of the CE web server I'm trying to connect to. Now
I've found a couple things in my Google-travels, one was a comment
about making sure UseUnsafeHeaderParsing = true if using .NET 2.0
(tried that). I also made sure that the user account I created existed
(verified in registry of device, and when I access the default web
page I'm prompted and the account works). I have even restarted the
web service after creating the account, just to make sure. I've even
tried using the default "admin" account that the WinCE image has built-
in.
So what am I missing? Here is my current Reg-setup for the web server:
[HKEY_LOCAL_MACHINE\COMM\HTTPD\VROOTS\/]
@="\\windows\\www\\wwwpub\\"
"a"=dword:1
"Basic"=dword:1
"NTLM"=dword:1
I've tried it with and without the NTLM setting; with and without a
defined UserList; and now I've run out of ideas (and info, as now all
new sites I find via Google show me the same suggestions I've already
tried <sigh>).
Has anyone dealt with this successfully? I'd appreciate any
suggestions.
Thanks!
Chris
.
- References:
- WinCE Web Server Auth Not working
- From: fuzz_ball
- WinCE Web Server Auth Not working
- Prev by Date: Re: Splash screen on Win CE SBC
- Previous by thread: WinCE Web Server Auth Not working
- Next by thread: Services in Win CE device
- Index(es):
Relevant Pages
|
