Hi Gurus,

I think this cookieless mode was made to save time.
I spent 3 days (tests on handset with slow connection) and my solution
still not solved.

I tried something basic

--------------------------------------------------------
C:\> telnet mydomain.tld 80

GET /default.aspx?param1=value&param2=value HTTP/1.1
Host: mydomain.tld
Accept: text/vnd.wap.wml

HTTP/1.1 302 Found
Connection: Keep-Alive
Date: Tue, 19 Oct 2004 16:30:16 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Location: /(b2x3aj45fpdvu255000fvzf0)/default.aspx?param1=value&param2=value
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 184

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a
href='/(b2x3aj45fpdvu255000fvzf0)/default.aspx?param1=value&param2=value'>here</a>.</h2>
</body></html>
--------------------------------------------------------

Q1: why response are in html content-type ?
Q2: why response contains html document whereas my client has no
capabilities to read it ??
Q3: why, on some handset, redirection takes only the first querystring
parameter.

Thanks for you help.
Have a nice day/night.

Antoine.

Re: IIS6 / Cookieless / Another annoying redirect issue with handset... by David

David
Wed Oct 20 02:06:33 CDT 2004

Your questions do not seem to have anything to do with IIS6 but rather
ASP.Net. I suggest you post your questions on an ASP.Net Forum, such as
www.asp.net or microsoft.public.dotnet.framework.aspnet

Q1 and Q2: IIS knows nothing about WAP -- the application layer (in this
case ASP.Net) is what needs to be configured to work with devices
automagically. Targetting mobile devices definitely work as an ASP.Net
feature, so you want to take your questions there.

Q3: That behavior depends on the mobile client. ASP.Net tells IIS to set
that Location: header, and it is sent to the client browser. What that
client does with the information, completely depends on it. At this point,
it sounds like a bug with mobile clients (in general, phone browsers all
sound to be pretty broken and buggy to me, based on questions posed -- I
mean, what do you think is more stable -- a server product with 3+ years of
development/testing or a client product with <1 years of
development/testing).

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Antoine Drochon" <antoine@NOSPAM-at-all.drochon.net> wrote in message
news:4175480d$0$32552$636a15ce@news.free.fr...
Hi Gurus,

I think this cookieless mode was made to save time.
I spent 3 days (tests on handset with slow connection) and my solution
still not solved.

I tried something basic

--------------------------------------------------------
C:\> telnet mydomain.tld 80

GET /default.aspx?param1=value&param2=value HTTP/1.1
Host: mydomain.tld
Accept: text/vnd.wap.wml

HTTP/1.1 302 Found
Connection: Keep-Alive
Date: Tue, 19 Oct 2004 16:30:16 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Location: /(b2x3aj45fpdvu255000fvzf0)/default.aspx?param1=value&param2=value
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 184

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a
href='/(b2x3aj45fpdvu255000fvzf0)/default.aspx?param1=value&param2=value'>he
re</a>.</h2>
</body></html>
--------------------------------------------------------

Q1: why response are in html content-type ?
Q2: why response contains html document whereas my client has no
capabilities to read it ??
Q3: why, on some handset, redirection takes only the first querystring
parameter.

Thanks for you help.
Have a nice day/night.

Antoine.