Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.

OK. Let's take a generic shopping application.

The user comes in at a top index, then clicks an atag to the shopping index. From there he clicks on a category atag (say, fruits) and is presented with Bananas and Blackberries, each of which has an "Add to cart" tag below them. But he also has the choice to click on Bananas itself and see a fuller product description. He does so, and decides to buy (atag to "Add to cart" script) from this level.

A return via HTTP_REFERER from the full description page should return him to the shopping index, but instead it sends him back to the main index.

This seems to be a general problem with browsers not being refreshed when atags are selected. As pointed out in 20776, issuing a meta-refresh fixed a similar problem on a return that wasn't working correctly. You may have already solved this if that bug is closed.

Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions. 

Thank you for your interest in PHP.

You should not rely on HTTP_REFERER for your application logic. HTTP_REFERER is sent by the client/browser and therefore not reliable.

On my system, it does report the correct HTTP_REFERER (as long as the browser sends one..)

Yup, this one's definitely bogus. Turned out to be a subtle error in the sample code I'm hacking around.