USE IE10 TO ACCESS MY LOCAL DEBUG WEBSITE HAS ERROR

http://forums.asp.net/t/1928245.aspx

 

USE IE10 TO ACCESS MY LOCAL DEBUG WEBSITE HAS ERROR.

Aug 09, 2013 07:13 AM|LINK

i use VS2010 ,and i upgrade to IE10 recently

when i run my web app （ASP.net development server） ，in IE10 the address auto change to

http://localhost:10992/(F(7HiB_Hok0Jhqmdpn0KQBIyj74QeW6PKxuHulmoWr2XkfBhUuO_Ix9lzOHSe610QzALBve-Ka_iIn6Gdtfh-E_TJ3RhbqEZnp0he1xTgF2SOkBz7xTbNn6eT7oXt2xDO6uxvk1vl9VtTcU-Us2XRTQ9EMP1n4QtUZFLJtrj3J8b0nRxhvq_u-pBXIqhgN_FHS0))/AuthorizationVIR/Index

Ii shoud be：http://localhost:10992/AuthorizationVIR/Index
is there anyone can help me to have a look? 

 

Aug 11, 2013 05:04 PM|LINK

ASP.NET checks the user agent string to detect browsers. However, as the version numbers increase, ASP.NET does not recognize new version of IE10 and handles it as an unknown browser and does not send back a Set-Cookie header. This is then undestood as browser without cookies support and adds a session string to the URL (cookie less sessions). 

There is a hotfix available for this at http://support.microsoft.com/kb/2600088/en-us. After that it should work.

More info at

http://forums.asp.net/t/1838010.aspx/1
http://stackoverflow.com/questions/6983732/ie10-user-agent-causes-asp-net-to-not-send-back-set-cookie-ie10-not-setting-coo4

Hope this helps.

 

http://support.microsoft.com/kb/2600088/en-us

 

 

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

IE10 User-Agent causes ASP.Net to not send back Set-Cookie (IE10 not setting cookies)

http://stackoverflow.com/questions/6983732/ie10-user-agent-causes-asp-net-to-not-send-back-set-cookie-ie10-not-setting-coo

 

The problem rests with some IIS instances thinking that IE10 is a cookieless browser (i.e. cant support cookies). In our problem case the server was setting the authentication cookie and sending it back to the browser, but was then ignoring the cookie on subsequent requests.

The solution is to either patch the browser capabilities so that it knows IE10 can do cookies (outlined in another answer on this page), or change the default behaviour to force it to use cookies even if it thinks the browser can’t do cookies.

We just added the following to our forms section in web.config:

cookieless="UseCookies"

<authenticationmode="Forms"><formsname=".AUTH"cookieless="UseCookies"loginUrl="/"timeout="10000"path="/"/></authentication>