From: MCM14 on 7 Jul 2010 09:44 I am building a web service handler that implements: System.Web.IHttpHandler and System.Web.SessionState.IRequiresSessionState It works well, except for 1 problem with Session State. When the Session mode is set to InProc, everything works correctly. When I change the Session mode to StateServer, the Session becomes read-only. Session works in StateServer mode throughout the rest of my application, but for some reason it becomes read-only in the context of my handler. Please let me know what is causing this.
From: Allen Chen [MSFT] on 11 Jul 2010 23:07 Hi, The common issue that may cause this behavior is you probably set EnableSessionState to ReadOnly in web.config: <pages enableSessionState="ReadOnly"></pages> Please check it first. In InProc mode the ReadOnly setting may not have the effect as you might thought so it appears to be "everything works correctly". Please see the following FAQ for more details: http://forums.asp.net/p/7504/7504.aspx: Quote: Q: I set EnableSessionState to "ReadOnly", but in InProc mode I can still modify the session. Why is that? A: Even those enableSessionState is marked as ReadOnly, but in InProc state, the user can still modify the session. The only difference is that the session will not be locked during the request. This limitation is by-design. And I sorry that it�s not documented in MSDN. If it still doesn't work could you send me a demo that can reproduce this problem? My email is allenc(a)microsoft.com.Please update here after sending the project in case I missed that email. Regards, Allen Chen Microsoft Online Support Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com. ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications. Note: MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 2 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
From: Allen Chen [MSFT] on 13 Jul 2010 21:37 Hi, >It works well, except for 1 problem with Session State. When the Session >mode is set to InProc, everything works correctly. When I change the Session >mode to StateServer, the Session becomes read-only. Session works in >StateServer mode throughout the rest of my application, but for some reason >it becomes read-only in the context of my handler. >Please let me know what is causing this. Have you resolved this issue? Regards, Allen Chen Microsoft Online Support Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com. ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications. Note: MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 2 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
|
Pages: 1 Prev: Running problem Next: export gridview to excel format error |