PHP & htaccess

[atrum]

I'm not sure if this quite qualifies as a PHP question, but I was trying something that involved passing information across pages using session variables, when i noticed some odd values being stored and retrieved.

The pages use a wiki style parser in the htaccess file to make browsing simpler (similar to http://meta.wikimedia.org/wiki/Talk:Main_Page ).

My question is; does the effect of the htaccess parser cause the page to get a double hit? I traced the the contents of the variable at the very beginning and end of the page and the results show that there is additional information storing between page loads.

Let me know if it's not clear what I'm asking.

Thanks.

[bradgrafelman]

That would entirely depend upon the contents of the .htaccess file in question and how the redirect is being done.

For a simple RewriteRule, though, no, the only "hit" that will take place is wherever the final resulting rule redirects the request.

[atrum]

Options -Indexes +FollowSymlinks
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^:]*):(.*)$ /index.php?a=$1&p=$2 [L]

I am indeed using the rewrite rule, I'm not sure what else could possibly be causing it if it is not this.

I added in a single simple SQL insert query at the top of the page and checked the database after refreshing just once, and i found 2 separate entries. I did this a few times and each time after refreshing just once, i found 2 more entries each time.

I'm not saying I don't believe you when you say the rewrite rule doesn't cause a double hit, but I don't know what else would be causing it.

[bradgrafelman]

Do you see the superfluous inserts if you view and refresh the index.php page directly (giving it the proper parameters via the query string, of course)?

[atrum]

excuse me, i posted my local htaccess, not the one on the server...

Options -Indexes +FollowSymlinks
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^:]*):(.*)$ /index.php?a=$1&p=$2 [L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^:]*)$ /index.php?a=$1 [L]

The 2nd rule was for single variable commands, for some reason I couldn't get a single hyrbid rule to work.

I don't know why I didn't try testing direct file access before... but I did and it double posted again. I also tried test.php, which is just a blank file i uploaded, and it did a single post to the database...

That would seem to imply it's my rewrite rule that is off then, though I'm not sure what.

[bradgrafelman]

If you accessed the index.php directly and it double posted, then I fail to see why that would "seem to imply it's [your] rewrite rule that is off" since you've effectively taken mod_rewrite out of the equation altogether... ?

[atrum]

test.php is a blank file I uploaded,

and accessing it directly it posted to the database, once.

What could be causing that? the specific code to post to the table only exists in the index.php code.

the reason i said it implies it would be the rewrite is because if the code only exists in the index.php, there's no way that test.php could cause a data post, so that would make me think the rewrite rule was doing something to call the index.php code.

I refreshed test.php several times to double check my observations.

[atrum]

sorry for the double reply...

but I tried refreshing test.php, saw the single post, deleted the query call at the top of index.php and then refreshed test.php again and there was no database post. accessing test.php is causing index.php to load, and if it's not the re-write rule doing something funky, what else can cause this issue?