Timeline for When & why I need to use web.AllowUnsafeUpdates = true
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 19, 2015 at 17:37 | vote | accept | jobin | ||
| Apr 10, 2015 at 11:57 | comment | added | jobin | yes, but why? with asp.net, I can insert row to database without things such this. | |
| Apr 9, 2015 at 20:39 | comment | added | Waqas Sarwar MVP♦ | @jobin Say you have a list and you want to update something to the SharePoint data [content DB], then you need to set AllowUnsafeUpdates = true for the web and after you have done you need to set it back to false. | |
| Apr 9, 2015 at 20:32 | comment | added | Ashley | @jobin because SharePoint. | |
| Apr 9, 2015 at 7:24 | comment | added | jobin | unfortunately i can't understand the answer, it seem correct, but is there an simple way to describe it. why we don't need something like this with ASP.net Applications? | |
| Apr 8, 2015 at 7:46 | comment | added | Alexey Krasheninnikov | I think there's still an error. You need unsafe updates allowed to make updates during the processing of a GET request, not to GET data from database. | |
| Apr 7, 2015 at 1:39 | comment | added | Paul Schaeflein | This answer is correct from a technical perspective. However, there are no valid scenarios in which custom code should use AllowUnsafe. If you are writing custom code, you should use the FormDigest or first make a call to _api/contextinfo. | |
| Apr 6, 2015 at 15:55 | history | answered | Waqas Sarwar MVP♦ | CC BY-SA 3.0 |