![]() |
|
[Help] HTTP realm was not really that easy! - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444) +--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151) +---- Forum: Coders Lounge (https://hackforums.net/forumdisplay.php?fid=5) +---- Thread: [Help] HTTP realm was not really that easy! (/showthread.php?tid=4088610) |
HTTP realm was not really that easy! - pwntoken - Feb 28, 2014 Yes the HTTP realm might seem so easy at the first go, but however taking a look at the original RFC from 1999, I really could not pick up certain aspects to what this does. Like the HTTP-realm describes the string for the WWW-authenticate headers and does give the auth-scheme a name, but read closer at this. Quote: The realm directive (case-insensitive) is required for all First half. Quote: The realm directive (case-insensitive) is required for all realm directive could be case-insensitive, but realm value could not be? and the realm directive was supposed to be the realm header itself of the value which the web developer chooses to set? Quote:in combination with the canonical root URL (the I do not really understand what does it mean to say! what is more important about 'in combination'? what has to be combined here? Others I could get the notion of what realm does. * - pwntoken - Mar 3, 2014 doesn't matter, got the answer... wrote papers on it too.. I wonder how hackers here go without getting to these basics and call themselves hackers. That lags the generation apart and creates a divide between the skids, anti-skids, pro and the REAL ones. Some are wannabe pro's, acting as if they know PHP and MySQL and could do SQLi at core, attains the 'hacker' position! * - Eight - Mar 4, 2014 Well you're right in saying it ain't easy.. The HTTP protocol has a lot of ramifications, I know this because I tried to write clients from scratch in the past (still do), even basic ones, but I always fail to make my code 100% compliant. This makes me appreciate tools like cURL and wget. Kudos on managing to decipher the RFC. When you say you wrote a paper on it, was it like an academic research/school project thing ? * - pwntoken - Mar 4, 2014 (Mar 4, 2014 11:00 AM)Eight Wrote: Well you're right in saying it ain't easy.. The HTTP protocol has a lot of ramifications, I know this because I tried to write clients from scratch in the past (still do), even basic ones, but I always fail to make my code 100% compliant. This makes me appreciate tools like cURL and wget. No, I wrote the paper from the scratch as per my personal research. I don't have to do when the university orders me! I am keeping this because I wanted to learn more.. that's all. And currently it's not half the RFC's I had covered, because of too many ongoing changes, it keeps changing due to newer drafts. What I am keeping track of is the common ones which remains from protocol 0.9, 1.0, 1.1 to HTML5 which will be supporting 2.0 That been said, I have completely dedicated 1 month study of protocols itself. The web application level protocols is the first target I am finishing. |