Timeline for Access to raw html source code after angular client side processing
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 3, 2016 at 18:56 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 4, 2016 at 17:57 | history | edited | Jedi | CC BY-SA 3.0 |
added 5 characters in body
|
| Aug 4, 2016 at 17:11 | answer | added | Baruch Spinoza | timeline score: 0 | |
| Aug 4, 2016 at 16:24 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 5, 2016 at 19:04 | comment | added | dandavis |
there is no such thing as dynamic raw source code, and how the DOM gets serialized has little/nothing to do with XSS vulnerabilities. so, while document.outerHTML contains the closest thing to what's described, there's no point in looking at it: If you don't see the alert, the script is safe...
|
|
| Jul 5, 2016 at 15:28 | history | edited | Sibwara | CC BY-SA 3.0 |
added 925 characters in body
|
| Jul 5, 2016 at 14:58 | answer | added | Lorenz | timeline score: 1 | |
| Jul 5, 2016 at 14:18 | history | asked | Sibwara | CC BY-SA 3.0 |