Jump to content

megosh

Members
  • Posts

    12
  • Joined

  • Last visited

    Never

Profile Information

  • Gender
    Not Telling

megosh's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. I'm not very experienced with IIS7 but this page seems to have solved all of my .htaccess file issues. You'll need to import them into a rewrite rule. I followed the guide from IIS7's website located here: http://learn.iis.net/page.aspx/470/importing-apache-modrewrite-rules/
  2. Yep, that was the problem. Everything is working perfectly. Thank you for your help, PFMaBiSmAd.
  3. At first glance, that appears to be the cause... However I'll be unable to change anything until later this evening. Will report back here with results, thanks for your quick responses.
  4. session.gc_divisor 1000 1000 session.gc_maxlifetime 1440 1440 session.gc_probability 1 1 Direct copy-paste from phpinfo();
  5. I've been doing some snooping around my dedicated to try and pinpoint the root of some lag spikes my game server has been encountering. Though I'm not entirely sure if this applies, it doesn't seem right. I'm running IIS7 with PHP 5.2.13. I found a massive (300,000+) number of sess_vvvv7ek73ce8f9hmns5i717762 (example) files in the save path: C:/Windows/Temp/. All but 15 have the prefix "sess_%". I've come to the understanding that these files should be cleaned by PHP every so often to prevent this from happening, though its clear its not actually doing that. I've looked through my php.ini and the most I found was that it was to clean those files after 24 mins or 1440 sec: session.gc_maxlifetime = 1440 I'm not entirely sure if this is the setting that specifically controls cleaning these files, but this is the best I could find. I've done a fair amount of searching on google but the best result I could find was a batch file that cleared out all "sess_" files every 24 hours. Does anyone know the cause of this problem? Any and all help would be greatly appreciated. - Doug
  6. Quick question... Doesn't if($_POST) do the same as if(isset($_POST))? What if I only want one portion of the post, if per-say I'm using multiple <input type='text' name='Test1'> <input type='text' name='Test2'>... Simply checking for if(isset($_POST)) wouldn't do what is required. Then what would the difference be between if(isset($_POST['Test1']) and if($_POST['Test1'])? I'm using both if(isset($_POST['test'])) and if($_POST['test']) in different places, and have experienced the problem with both. I'll try changing them all to isset() and will report back in a day or so. Thanks for the move and the attention.
  7. I'm not entirely sure what you mean... The code I posted in my first post is what processes the form.
  8. I'm not entirely sure what you were asking, so I assumed this: <html> <body> <form action="/test.php" method="POST"> Test: <input type="text" name="test"> <br> <input type='submit' name='Submit' value="Submit"> </form> </body> </html> copy-paste from view-source:http://localhost/test.php
  9. I'm really at a loss... everything on my site that uses post is affected by it. Though a VB forum were running has no issues at all, so it can't be something weird with apache.
  10. There is: http://pastebin.com/bZtEWmeA which is used on every page for an expanding menu http://pastebin.com/mqCNreAC for an in-window popup (not called on any of my pages containing $_POST) http://pastebin.com/AnkbzqgX to replace the current in-window popup (not called on any of my pages containing $_POST) http://static.wowhead.com/widgets/power.js called on almost all pages
  11. Hi, I've got a small problem that has been annoying me for a long while. In short, I've had a few pages that require the user to enter information and it creates an account for them... They work 99% of the time for all users... however, I do get some situations where users experience an inability to submit the page. Basically saying that hitting the submit button does nothing but refresh the page. This does not appear to be browser specific and can usually be solved by restarting the user's browser. (or in chrome opening a new tab) Here is some code from my creation page that has this problem. I edited out all the sql things and replaced it to keep it simple. I have personally experienced the problem stated in about 1 in 100~ tries. <html> <body> <?php if ($_POST['Submit']) { //do stuff echo "information entered: ".$_POST['test']; } else { ?> <form action="<?php echo $_SERVER['PHP_SELF']; ?>" method="POST"> Test: <input type="text" name="test"> <br> <input type='submit' name='Submit' value="Submit"> </form> <?php } ?> </body> </html> Does anyone have any possible insight into the cause of this problem, or what coding style I can adopt to prevent it from happening? All input is appreciated. Kind regards, Doug
  12. Wow, sorry please delete this... I found a solution to my problem within 5 mins after posting this.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.