Hi guys

Just want to clarify this if you have sessionState mode="StateServer" and Cookieless="false", and the user browser doesn't allow to have a cookie for unknown reason for instance what is going to be? Does this mean session will time out straightaway?

I know that you can set to Cookieless="true" what other impact on this beside putting extra characters in the URL?

What is the best practice anyway to hanle this? Should I warning the user that that browser is not supported?!?!

I am appreciated you comment.

Thanks

If your app will not need cookies for anything other than managing state (no authentication or other info passing), then there wouldn't be any reason not to use cookieless other that the extra characters on the url and the potential impact that might have for search engines accessing your site.

 Currently, most sites just add a message on the home page that cookies are required for deeper access.

We are using session (cookieless="false") mainly for authentication and passing info. So if turn on the cookiless="true" ... what is the impact then? I know that the it will have an extra characters in the URL and obviosly no cookies. Is there any impacts though?

Thanks 

Hi All,

I have gone through this threat, and my problem is new.

I have test SessionState running very well in my local server. but when deploy to Hosting Server, it doesn't work. It show the following message.

-------

Configuration Error

Line 37: 				<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/></assemblies>
Line 38: 		</compilation>
Line 39: 		<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="...." /><httpHandlers>
Line 40: 			<remove verb="*" path="*.asmx"/>
Line 41: 			<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

Source File: ..\web.config    Line: 39

------------------

 I don't know the asp_state.exe is running or not, but i believe it is running. I am waiting the Hosting Company to answer this. But, if the "aspnet_state.exe" is not provided from hosting Company, is there any thing we can do to make this work?

Best,

Pakk

Usually this error just means that the folder containg the newly deployed application hasn't been tagged as an application in IIS.  I don't think it's really complaining about SessionState.

mode="InProc" (as you have it) enables in-process session state.  Even though you've specified a connection string for state server, in won't be used.

Also, you can't set the <sessionState> section in a sub-project/folder.  It can only be set in the top level web.config of your site.