Jump to content

Search the Community

Showing results for tags 'timeout'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to PHP Freaks
    • Announcements
    • Introductions
  • PHP Coding
    • PHP Coding Help
    • Regex Help
    • Third Party Scripts
    • FAQ/Code Snippet Repository
  • SQL / Database
    • MySQL Help
    • PostgreSQL
    • Microsoft SQL - MSSQL
    • Other RDBMS and SQL dialects
  • Client Side
    • HTML Help
    • CSS Help
    • Javascript Help
    • Other
  • Applications and Frameworks
    • Applications
    • Frameworks
    • Other Libraries
  • Web Server Administration
    • PHP Installation and Configuration
    • Linux
    • Apache HTTP Server
    • Microsoft IIS
    • Other Web Server Software
  • Other
    • Application Design
    • Other Programming Languages
    • Editor Help (PhpStorm, VS Code, etc)
    • Website Critique
    • Beta Test Your Stuff!
  • Freelance, Contracts, Employment, etc.
    • Services Offered
    • Job Offerings
  • General Discussion
    • PHPFreaks.com Website Feedback
    • Miscellaneous

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








Donation Link

Found 3 results

  1. I'm trying to figure out how to keep a script executing after it reaches the timeout limit. It has always worked fine on PHP 5.2, but I just updated to PHP 5.4 and now scripts immediately quit executing after the allotted time. Brief summary of my problem: I have two pages in my site's admin panel that usually take some time to run. The first crunches some data and displays the results. It sometimes will time out before completing, but if you wait a moment to let it finish in the background and then refresh your browser, it'll display almost immediately, since MySQL has cached the results. A second page has to update a lot of records and sometimes will time out. I need the final output of the script, so after the rows update I log the output to a txt file which I can FTP in and read if need be. This is how things used to work, but now after the upgrade, when the page times out, script execution stops, and for the latter script that means that rows get updated but no log is ever created, which is a problem. I have tried: set_time_limit(0); ignore_user_abort(true); No effect. I think set_time_limit(0) fails to work because Apache itself times out? Although when the PHP timeout is set to 50, and Apache timeout set to 60, and it seems like execution stops at 50. (We're actually using Litespeed instead of Apache, but it reads the Apache ini file and everything. And we didn't update/change Litespeed when we updated PHP.) I don't want to raise the Apache timeout beyond 60 for sake of DDoS issues (we've been attacked before). From my understanding there's no way to raise the limit for just one page. I found some things that I thought might do that, for Litespeed, but they had no effect: In my htaccess file: RewriteEngine on RewriteRule ^$ - [E=noconntimeout:1] RewriteRule ^$ - [E=noabort:1] Before upgrading PHP I poured over the list of changes on php.net, and never found anything related to this. I've been relying on execution after the timeout for years (for these same two pages), so the sudden change and lack of a solution so far is strange to me. I could attempt to separate some code into chunks and on a cron, but I'd rather not. Any ideas? Thanks!
  2. I need to increase the session length for my app, it keeps timing out on the people using it.. just changing the default in my php settings would be great but I haven't found anything that's worked for me on-line, is anyone able to help?
  3. I've written a basic php application with a login feature, using $_SESSION, but it times out after 20 minutes, how can I change the length of a session? Either in php on the page or in the php files whichever is simpler.
  • 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.