Header Problems

larand

Hi! Being sick and tired of the darn ugly usrls (ie: http://www.phpbuilder.com/board/newthread.php?action=newthread&forumid=10)

I decided to try and send the variables through POST Headers, without using a form. Well, I found some code online, but am unsure if I am using it properly, here it is:

// Generate the request header

$URI = "www.torusmedia.net/users/mn_devel/alefort/news/test.php";
$ReqBody = "test=1";
$Host = "www.torusmedia.net";
$ContentLength = 4096;

$ReqHeader =
"POST $URI HTTP/1.1\n".
"Host: $Host\n".
"Content-Type: application/x-www-form-urlencoded\n".
"Content-Length: $ContentLength\n\n".
"$ReqBody\n";

// Open the connection to the host
$socket = fsockopen($Host, 80, &$errno, &$errstr);

$idx = 0;
fputs($socket, $ReqHeader);
while (!feof($socket))

$Result[$idx++] = fgets($socket, 128); 

print_r($Result);

and this is the output I get from this:

http://www.torusmedia.net/users/mn_devel/alefort/news/test.php

If anyone has any insight, or has played most extensively with headers before, feel free to share this info. Thanks to all in advance!

matt_4013

Take a look at this: http://www.azmoo.net/index.php?page=3&tut_id=1

ksandom

WooHoo! That looks fun 😉

Some its I noticed. Should:

"POST_$URI_HTTP/1.1\n".

be:

"POST_".$URI."_HTTP/1.1\n".

(I notices a few occurances of this type of thing in this code.)

I've successfully done it in the past writing raw HTTP, however that doesn't help you here.

Is the URL the only thing you are trying to stop? I'm guessing you are trying to have links to specific places. You could get rid of them using javascript to fill in hidden things (sorry, that word has just completley escaped me!), and then using the "OnCLick" event to trigger changing those values and triggering the post action.

Personally, I would prefer using the URLs to a solution like this, it just doen't seem worth the effort.

Weedpacket

Presumably of course you'd be wanting the information in the querystring to be passed somehow (otherwise why would you be passing it at all?). One quite elegant solution is to rewrite the URL so that it's of the "domain/path/file.html" format, without the following querystring. So that your example URL could instead look like, say,

http://www.azmoo.net/3/1/tutorial.html
It's the job of the web server to figure out which resources go with which URLs. In this case, it would take the above and go "ah, a tutorial! So the last 'directory' is really the tut_id, and the 'directory' before that is really the page! That means the real URL is
http://www.azmoo.net/index.php?page=3&tut_id=1" and it would serve that.

Of course, that's not the only way you might tidy the URL. Alternates include:
http://www.azmoo.net/3/tutorial1.html
http://www.azmoo.net/page3/tutorial1.html
and so forth.

How exactly you achieve such "URL rewriting" (as it's called if you want a phrase to search on) depends on what web server you're using; in Apache this is handled by the mod_rewrite module.