Re: Session ID in Query Parameter?
From: Uwe (ub_at_liant.com)
Date: 03/06/04
- Next message: Joe Fallon: "Re: Context looses the ISitePrincipal..."
- Previous message: Dan Brussee: "Re: Code-Behind variables"
- In reply to: Steven Cheng[MSFT]: "RE: Session ID in Query Parameter?"
- Next in thread: Steven Cheng[MSFT]: "Re: Session ID in Query Parameter?"
- Reply: Steven Cheng[MSFT]: "Re: Session ID in Query Parameter?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Mar 2004 23:26:43 -0600
Hi Steven:
Thank you for your reply. My comments are interspersed below.
"Steven Cheng[MSFT]" <v-schang@online.microsoft.com> wrote in message
news:A$ETlqyAEHA.2300@cpmsftngxa06.phx.gbl...
> Hi Uwe,
>
> Thanks for posting in the community!
> From your description, you'd like to use the cookieless session in
> ASP.NETweb app. And the problem is that you've some non-ASP.NET/normal
html
> pages. So when posting from such normal html page the session state will
> lose(a new one start). Also, you'd like to looking for some certain
> appraches to resolve such problems, yes?
>
> As for this question, the ASP.NET buildin cookieless session support does
> lose some features that cookie-managed application provides. Those
> functions such as Form-based authentication, neat/custom urls, problems
> with mobile applications, or the ability to POST data from an html page
> become a thing of the past. Though the ASP.NET buildin hasn't provide some
> certain approachs on this, some other thiry-party members have tried some
> custom means to workaround this, here are some certain weblinks discusing
> on such topics:
>
> #Enabling POST in Cookieless ASP.NET Applications
> http://www.developer.com/net/asp/article.php/2216431
I had previously looked at this article, but it's a complex solution--not
from the implementation point of view, but I am concerned that there is
still a redirection involved. The browsers that I am supporting have
cookies disabled for security concerns, and I am concerned that they may
also have Javascript disabled. This solution uses Javascript to repost the
form data before the redirection.
> #Cookieless data persistence is possible
>
http://web.zdnet.com.au/builder/webdesign/scripting/story/0,2000040414,20273890,00.htm
Unfortunately, this article doesn't tell me how to use the ASP.NET Session
object in a cookieless way. I am trying to convert an existing "shopping
cart" ASP.NET program that is populated through the POST from various other
forms on the website. It uses the Session object and I really don't want to
change that.
> Also, since it's not the build in mechanism, it can't be guarantee that it
> won't work into any problem some time. In addition, I still think it
better
> to convert most pages into ASP.NET page (at least add mapping ) so as it
> also possbile to be handlered by ASP.NET runtime so that we can do some
> operations on those reponse stream.
Long-term, ASP.NET is the way to go. But like I said, others maintain the
HTML order forms in FrontPage that POST to the ASP.NET application. Less
work for me!
So, to restate the problem: there must be code in ASP.NET that takes the
session ID, looks for an existing session object and if found, connects to
it. If not found, it creates the object and session ID. I want to provide
the session ID string, rather than have the existing code read the session
ID string from the cookie.
Is there a place I can hook or subclass the code that creates/connects to
the session object?
--- Uwe
- Next message: Joe Fallon: "Re: Context looses the ISitePrincipal..."
- Previous message: Dan Brussee: "Re: Code-Behind variables"
- In reply to: Steven Cheng[MSFT]: "RE: Session ID in Query Parameter?"
- Next in thread: Steven Cheng[MSFT]: "Re: Session ID in Query Parameter?"
- Reply: Steven Cheng[MSFT]: "Re: Session ID in Query Parameter?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|