Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: GET and POST Methods Accepted |
|---|---|
| Date: | Thu, 13 Oct 2005 18:04:22 -0000 (GMT) |
Anyway I share this only because the original post seemed to focus on GET vs. POST more than XSS. I restrict GET as much as possible in site development because it can expose the inner workings of the site and secure methodology or not, we all miss something from time to time.
I don't understand this philosophy. If you forget what is visible in the web browser and look at what is put on the wire, which is trivially viewed with packages like ethereal, the only difference between GET and POST requests is that the parameters for GET requests are on the request line and parameters for POST requests are in the body. To me the security implications are practically identical.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: myspace hack, rSYN |
|---|---|
| Next by Date: | Re: User verification questions, Gary Gwin |
| Previous by Thread: | RE: GET and POST Methods Accepted, Derick Anderson |
| Next by Thread: | RE: GET and POST Methods Accepted, Joe Teff |
| Indexes: | [Date] [Thread] [Top] [All Lists] |