Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6106587
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T14:05:44+00:00 2026-05-23T14:05:44+00:00

I am not sure if it is a bug or configuration error but I

  • 0

I am not sure if it is a bug or configuration error but I keep getting ajax requests “canceled” at exactly 120 seconds. No http response code given.

The server side is running on a LAMP stack and the php max_execution_time is set to 240 seconds using mod_php5

Oddly enough, if I request the same page without ajax, it won’t timeout after 120 seconds.

Early tests shows that firefox does the same thing.

Can anyone help with this bug/annoyance?

Sample code

set_timeout_limit(o); 
sleep(1000);
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T14:05:45+00:00Added an answer on May 23, 2026 at 2:05 pm

    try to add timeout: xxx (in ms) to your AJAX call

    example:

    $.ajax({
      url: "test.html",
      timeout: 240000,
      context: document.body,
      success: function(){
        $(this).addClass("done");
      }
    });
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am not sure if this is a bug - but in this example
Sounds easy, but I've got a bug and I'm not sure what's causing it?
This is not a real bug BUT for sure it is not what you
I'm not sure whether it's a bug or what. But it's making my life
I think I've encountered a bug in Params::Validate , but I'm not sure whether
Not sure, but I think this may be a bug? Here is my model:
Not sure if this is a bug but it's not doing what I expect.
I am not sure this is a bug or not but at times when
I guess I've found a G++ bug but I'm not sure. I cannot explain
I'm not sure what is the root cause for getting such error(Heap Corruption) from

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.