<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Default network timeout may kick in before XHR timeout"
   href="https://bugs.webkit.org/show_bug.cgi?id=149704">149704</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Default network timeout may kick in before XHR timeout
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>WebKit Nightly Build
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>WebCore Misc.
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>youennf&#64;gmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>As pointed out by ap in <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - XHR2 timeout property should allow late updates"
   href="show_bug.cgi?id=98156">bug 98156</a>, <a href="http://trac.webkit.org/changeset/189445">http://trac.webkit.org/changeset/189445</a> introduces the fact that default networking timeout becomes a max timeout for all XHR requests.

If a web app sets a XHR timeout above the default network timeout, the default network timeout will kick in.

Setting networking timeout to infinite (or a sufficiently large value) for all XHR requests may work.

Setting networking timeout to infinite for all XHR requests that have their own timeout may work.
In that case, one may want to add special handling for the case of a web app that sets back the timeout to zero.
Ideally, the XHR timer should then be set to the default networking timeout value.
Infinite may be good enough, although not entirely satisfying.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>