NoComment

First of all, thank you for the quick reply. Sorry about that, but it didn't help much. I don't need to deal with site maps or such, I just need an answer to my 2 questions, since their answer is important to the design of my site.

Hi! Two questions: 1) I have been reading an article (http://www.zend.com/zend/spotlight/searchengine.php?article=searchengine&kind=sl&id=4863&open=1&anc=0&view=1 ) which basically said that search engines will tend to ignore pages which contain GET parameters in their links... (e.g. www.example.com/thread.php?id=391). Now my question is: Do I have to avoid GET parameters to make all of my pages accessible over, let's say, Google? Or is this article simply out-dated (it says it was written in 2001)? 2) Is there a way to successfully return a page, but tell the user agent that the URL of the returned webpage is actually different from the one the user entered? An example: The user opens www.example.com/thread.php?id=392 The server successfully returns the webpage, but tells the user agent, that the correct URL is actually "www.example.com/thebestthreadintheworld". Then the user agent automatically changes the URL in the address bar to the new URL, so when the user should bookmark it, the new, but correct URL is saved. What is important to me: I don't want use redirecting via header("Location: ...")-- and I don't want to use .htaccess. Is there a way to do that? Any comment would be appreciated, Thanks

No one has an idea?

Hi there! I'm currently looking for a way to implement mutexes in PHP/MySQL. I wasn't sure if it belongs into the PHP forum or rather into the MySQL forum. So I apologize if it's in the wrong forum. Imagine PHP script #1 tries to access a MySQL database and reads data from a table. At the same time PHP script #2 is executed, which tries to delete the very data script #1 is currently trying to read. This is especially problematic if script #1 has to read from the database multiple times, process the read information, read from the database again, etc, while the 2nd script is deleting this data. Is there a way to prevent that--so that PHP script #2 waits till PHP script #1 has done all its work and THEN deletes the table? Of course, the above mentioned situation is only an example, and I don't need a fix for THIS specific example, but I need to find a more generic way to implement mutexes/semaphores. Does anybody have an idea on how to do that? Thank you in advance!

Ok... a little update on my problem... I found just ANOTHER variable that could be used: $_SERVER['X_COMING_FROM']. I also found out that some of these header lines (those with a 'X') are probably not supported by the official RFC, but are still widely used. Anyone got an idea yet (or an answer to my above questions)?

Hi all. This is my first post on this forum, so please bear with me. I've got a question concerning the headers sent by the client accessing your page. I have found there are several variables accessible in PHP: $_SERVER['REMOTE_ADDR'] (which should not be determined by any HTTP headers, but by the web server reading the TCP/IP headers, right?) $_SERVER['HTTP_VIA'] (which will be filled if there is a transparent proxy) the above are pretty clear and cause no problems. But when you continue to search for headers that can possibly be sent by a client (may it be a proxy or not), it's getting very confusing: $_SERVER['HTTP_X_FORWARDED_FOR'] $_SERVER['HTTP_CLIENT_IP'] $_SERVER['HTTP_PROXY_CONNECTION'] $_SERVER['FORWARDED_FOR'] $_SERVER['X_FORWARDED_FOR'] $_SERVER['X_HTTP_FORWARDED_FOR'] $_SERVER['HTTP_FORWARDED'] I mean, they all seem to denote the SAME thing. Why use SEVEN different headers for that? Were the guys who wrote the RFCs bored? Why confuse people with so much possible headers, when it could be in ONE SINGLE header? Apparently this is not a PHP problem, since PHP just fills these variables by reading the HTTP header lines (X-Forwarded-for: , X-Forwarded: , ...) sent by the client. I have googled for all of those, but opinions seem to differ on what header line should be taken into account and what header line shouldn't. So, 1) Why are there so many possible headers? Are some of them obsolete? 2) What is the difference between those headers with a 'X' and those which lack the 'X'? 3) What is the difference between "FORWARDED_FOR" and just "FORWARDED"? Any help would be appreciated Thank you.