Re: Microsoft Mobile HTTP Server / Pocket IE question
- From: Roopak <Roopak@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Jul 2005 11:47:02 -0700
Thanks John for the response, it is a sideeffect of the fix, I was wondering
if this is a known issue and if there a workaround for that. Well I have been
waiting for quite some time, I guess its time to get paid support on this
issue.
Thanks
Roopak
"John Spaith [MS]" wrote:
> Sorry you haven't been getting a response on this. This sounds like it's
> some sort of side effect in connection manager of using the workaround XML
> to connect to http://localhost/ in the first place, but that's just a guess.
> I know very little about any of this so I'm afraid I can't help you here
> either.
>
> --
> John Spaith
> Software Design Engineer, Windows CE
> Microsoft Corporation
>
> Check out the new CE Networking Team Blog at 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. © 2003 Microsoft Corporation. All rights
> reserved.
>
> "Roopak" <Roopak@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:5FC59FF8-967C-4A82-80AB-DA2CC90780F5@xxxxxxxxxxxxxxxx
> > Hi John,
> > I have another odd problem associated with it, I have created another
> > thread
> > on that, but nobody replied, here is the posting once again:
> > -----------------------------------------------------------------------------------------------
> > I have a pocket PC 2003 device (iPAQ 5555, Ver 4.20.1081 (build 13100)), I
> > created a small webserver on pocketpc and I used internet explorer on
> > pocketpc to acess the webserver's html pages. The localhost fix in one of
> > the
> > FAQs ( adding a url mapping from 127.0.0.1 and localhost to a null
> > network)
> > works for me, but as soon as I do that
> > Under
> >
> > Setttings->Connections->Connections->Advanced->Network Card
> >
> > The drop list for "My network card connects to" becomes empty.!!!
> >
> > Why any idea?
> >
> > has anybody seen this issue, if yes any suggestions are welcome.
> > I am attaching the _setup.xml content that I used to create the .cpf file
> >
> > ----- _setup.xml
> > ----------------------------------------------------------------
> > <wap-provisioningdoc>
> > <characteristic type="CM_Mappings">
> > <characteristic type="536870911">
> > <parm name="Pattern" value="*://localhost/*" />
> > <parm name="Network" value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" />
> > </characteristic>
> > </characteristic>
> >
> > <characteristic type="Registry">
> > <characteristic
> > type="HKLM\Software\Microsoft\ConnMgr\Providers\{EF097F4C-DC4B-4c98-8FF6-AEF805DC0E8E}\localhost-null">
> > <parm name="DestId" value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}"
> > datatype="string" />
> > <parm name="Type" value="0" datatype="integer" />
> > <parm name="Enable" value="1" datatype="integer" />
> > </characteristic>
> > </characteristic>
> >
> > <characteristic type="CM_Mappings">
> > <characteristic type="536870911">
> > <parm name="Pattern" value="*://127.0.0.1/*" />
> > <parm name="Network" value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" />
> > </characteristic>
> > </characteristic>
> >
> > <characteristic type="Registry">
> > <characteristic
> > type="HKLM\Software\Microsoft\ConnMgr\Providers\{EF097F4C-DC4B-4c98-8FF6-AEF805DC0E8E}\localhost-null">
> > <parm name="DestId"
> > value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" datatype="string" />
> > <parm name="Type" value="0" datatype="integer" />
> > <parm name="Enable" value="1" datatype="integer" />
> > </characteristic>
> > </characteristic>
> >
> > </wap-provisioningdoc>
> >
> > ----------------------------------------------------------------------------------------------
> >
> > This fix is available but hardly any documentation regarding what each
> > tag/parameter means, its very difficult to guess what " <characteristic
> > type="536870911">" tag means or what are we trying to do by putting
> > type!!
> >
> > Any help is appreciated.
> >
> > -----------------------------------------------------------------------------------------------
> >
> >
> > "John Spaith [MS]" wrote:
> >
> >> The MS web server is never installed by default - you have to manually
> >> install it via the SDK, so this isn't causing the problem.
> >>
> >> I've dug into this a bit more and discovered that this is a known bug.
> >> The
> >> http://127.0.0.1 doesn't work but localhost will. The problems in the
> >> previous releases were that you could *never* connect to localhost
> >> without
> >> an elaborate workaround, whereas this one at least has a very easy
> >> workaround.
> >>
> >> Very sorry about this.
> >>
> >> --
> >> John Spaith
> >> Software Design Engineer, Windows CE
> >> Microsoft Corporation
> >>
> >> Check out the new CE Networking Team Blog at
> >> 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. © 2003 Microsoft Corporation. All
> >> rights
> >> reserved.
> >>
> >> "Chris Martinez" <ChrisMartinez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> message
> >> news:A597D7E9-C4BC-4895-954C-0C60E02132D2@xxxxxxxxxxxxxxxx
> >> > Yes, Windows Mobile 5.0 == PocketPC 2005. Oddly enough, what I have
> >> > found
> >> > is
> >> > that replacing 127.0.0.1 with localhost solves the problem. This is
> >> > somewhat
> >> > troubling.
> >> >
> >> > Also, I am not using the MS Webserver, I have an application that is
> >> > listening to a port on the localhost address. But your suggestion
> >> > makes
> >> > me
> >> > wonder if the MS Webserver might be colliding with my application.
> >> >
> >> >
> >> > "John Spaith [MS]" wrote:
> >> >
> >> >> I take it Windows Mobile 5 is PocketPC 2005 (I can't keep all the
> >> >> marketing
> >> >> jargin straight :(). If so my understanding was that this was fixed
> >> >> and
> >> >> is
> >> >> in a regression test for real now. Could you remove the patch
> >> >> entirely
> >> >> and
> >> >> see if this works and let me know.
> >> >>
> >> >> Also please make sure the web server itself was started properly by
> >> >> checking
> >> >> out \windows\www\current-httpd.log (or something like that) which
> >> >> would
> >> >> print out messages when HTTPD itself starts up.
> >> >>
> >> >> --
> >> >> John Spaith
> >> >> Software Design Engineer, Windows CE
> >> >> Microsoft Corporation
> >> >>
> >> >> Check out the new CE Networking Team Blog at
> >> >> 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. © 2003 Microsoft Corporation. All
> >> >> rights
> >> >> reserved.
> >> >>
> >> >> "Chris Martinez" <Chris Martinez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> >> message
> >> >> news:352A6459-148E-435B-B8FC-527ECBB507F6@xxxxxxxxxxxxxxxx
> >> >> > John,
> >> >> >
> >> >> > Has this problem been fixed in Windows Mobile 5? We have been using
> >> >> > the
> >> >> > loopback "patch" in our 2003 product; but when we tried the same
> >> >> > patch
> >> >> > on
> >> >> > Windows Mobile 5 (ARM emulator), we're back to the same old problem.
> >> >> >
> >> >> > "John Spaith [MS]" wrote:
> >> >> >
> >> >> >> This is a known bug on PocketPC 2003's. Check out
> >> >> >> http://groups.google.com/groups?q=PPC2003+PIE+will+not+connect+to+localhost&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=%23HNpjuBYDHA.3444%40tk2msftngp13.phx.gbl&r
> >> >> >> for a workaround. Sorry for the inconvenience this has caused you.
> >> >> >>
> >> >> >> This is also broken on PPC 2000 (but not 2002, oddly enough). The
> >> >> >> 2000
> >> >> >> fix
> >> >> >> is a lot more painful so hopefully you don't have to go down that
> >> >> >> route.
> >> >> >>
> >> >> >> --
> >> >> >> John Spaith
> >> >> >> Software Design Engineer, Windows CE
> >> >> >> Microsoft Corporation
> >> >> >>
> >> >> >> Check out the new CE Networking Team Blog at
> >> >> >> 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. © 2003 Microsoft Corporation. All
> >> >> >> rights
> >> >> >> reserved.
> >> >> >>
> >> >> >> "Josh" <Josh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> >> news:F9D271C5-FD69-475C-90C2-C211A0F86565@xxxxxxxxxxxxxxxx
> >> >> >> >I am trying to serve up some dynamic ASP pages on my PocketPC for
> >> >> >> >myself
> >> >> >> > using Microsoft Mobile HTTP Server & PocketASPBuilder. When my
> >> >> >> > PocketPC
> >> >> >> > is
> >> >> >> > connected to my computer, everything works perfect. However, when
> >> >> >> > I
> >> >> >> > disconnect the device and try to access the pages via Pocket IE
> >> >> >> > (http://127.0.0.1), I receive the Cannot Connect error message
> >> >> >> > even
> >> >> >> > though
> >> >> >> > I'm not wanting to connect to anything except myself. I've
> >> >> >> > searched
> >> >> >> > everywhere I can think of to search and I'm coming up blank. If I
> >> >> >> > connect
> >> >> >> > my
> >> >> >> > device and load all of the asp pages, Pocket IE will load the
> >> >> >> > cached
> >> >> >> > pages,
> >> >> >> > but then the content is not up to date for any changes I make. I
> >> >> >> > am
> >> >> >> > assuming
> >> >> >> > that I am having this problem because I have no network device to
> >> >> >> > install
> >> >> >> > even if I wanted to. Is there some sort of loopback network
> >> >> >> > device
> >> >> >> > that
> >> >> >> > I
> >> >> >> > can
> >> >> >> > install? Or is there another solution that I'm missing? Thanks in
> >> >> >> > advance
> >> >> >> > for
> >> >> >> > any help.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
> >>
>
>
>
.
- References:
- Re: Microsoft Mobile HTTP Server / Pocket IE question
- From: John Spaith [MS]
- Re: Microsoft Mobile HTTP Server / Pocket IE question
- Prev by Date: Re: Microsoft Mobile HTTP Server / Pocket IE question
- Next by Date: Network Traffic Monitoring
- Previous by thread: Re: Microsoft Mobile HTTP Server / Pocket IE question
- Next by thread: Network Traffic Monitoring
- Index(es):
Relevant Pages
|
Loading
