iis

I can’t access the site externally from IIS on docker

by

I have installed IIS on docker, disabled any firewall and configure no-ip for access externalLy, and finally configured no-ip on my router with port fowarding…
I have configured iis and congirured local port 91 to 80 container port…
from local ‘http://pincopallino-no-ip:91’ compare correctly the default iis page, but externally network I get ‘err_connection_timed_out’….

IIS end application on every request

by

I’ve notice that on the production server, my asp.net 4.7.2 application is very slow. By debugging I’ve found that in global.asax the Application_start and Application_end is called on every request, causing a recompile of the application each time and slowing down the response.
I0ve test it on several servers and the behaviour is always the same.
Running the website on localhost in IIS (not iis express) this not happen.
How can I check why Application_End is called and from where?
Debugging in VS the Application_end stacktrace is empty, I cannot see from where is called.

How do I get IIS to return a Custom-Cache Control Header from WebApi 2, IIS 10 returns private every time

by

** UPDATE Jan 27, 2021 **
I have been working with Microsoft on this issue and we did a request trace and reviewed the FREB log and confirmed that the code is outputting the correct headers but in the END_REQUEST handler they are replaced with cache-control private. After building several virtual machines from scratch we learned that out of the box, this problem doesn’t happen. However when we install the latest version of STACKIFY AGENT (4.29.29) once we put the agent on this behavior happens. Older versions of Stackify agent (RETRACE profiler and APM) don’t do this, but so far, this is irreversible: once we install 4.29.29 of Stackify, uninstalling or installing older versions doesn’t undo this issue, the environment is somehow permanently modified.

500 errors serving static content from ASP .Net Framework 4.5 sites using custom account in app pool

by

I have a few older ASP .Net Framework (web forms and mvc) sites on an IIS server which run in an app pool which uses a custom AD account. Serving any static files (images, js, css) from the Content folder of the site has always worked fine – but this began failing a few weeks ago. All requests for static content return a 500 error. The dynamic content still runs fine. When I switch the app pool to use the built-in ApplicationPoolIdentity, then the static content is returned fine. I verified that the custom AD account has read access to the static files on file system. There are no messages in the event log and the IIS logs only show the 500 response with no details. As this works fine using the built-in account, I am assuming the static file handler is still installed and running as expected.