Note that there are some explanatory texts on larger screens.

plurals
  1. POIIS handles request much longer when request originates from another computer and returns HTTP 200 and text
    primarykey
    data
    text
    <p>In my ASP.NET MVC3 application I have two very simple controller actions one of which returns <code>ContentResult</code> with a short piece of hard-coded text and another one returns <code>HttpStatusCodeResult</code> with code 403.</p> <p>The application is deployed, then a pack of requests is sent to the routes served by that controller actions several times from the same computer, then an equivalent pack of requests is sent to those routes from another computer. No configuration changes are performed in between, application pool is not restarted - nothing like that.</p> <p>I review the IIS logs and see that <code>time-taken</code> (the time the request spends inside the web server and not including any network latencies, DNS lookups, etc) is very different depending on whether the request was sent from the same computer or not and also depending on which of the actions was called. If it's from the same computer <code>time-taken</code> is around 15 milliseconds for both actions. If it's from another computer <code>time-taken</code> is around 260 milliseconds for the action returning <code>ContentResult</code> and around 100 milliseconds for the action returning 403.</p> <p>Clearly there's a dependency on whether any content is returned in the response body when the request comes from another computer.</p> <p>My code doesn't have any explicit logic that changes how requests are handled depending on their origin and result.</p> <p>What might cause the timing difference?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload