campinam

<div>
The app is newly created.<br />
I'd be interested if this behavior is normal (just needs settings) or not (other sites do have access to their apps).
</div>


<div>
<div class="content wysiwyg-content">
My web site has an web application in a subdirectory. I created first a virtual directory for it, then &quot;convert to application&quot;. Both the site and the app share the same pool.<br />
<br />
As long as I call a page of the app (a .aspx) directly through browser address, it works just fine. In addition, the app pages have non-restricted access to the hosting site's files.<br />
<br />
But if I call such a page from a .htm page on the site (a non-app page), ASP.NET Event 1310, Event Code 3006, and in the Request information section, User: Is authenticated: False.<br />
<br />
My guess was the account IIS uses to access a .aspx page directly is different from the account the web site uses to call such a page from one its own .htm pages.<br />
<br />
How can I fix this? (no experience with such issues) Server is 2019.
</div>
</div>


My web site has an web application in a subdirectory. I created first a virtual directory for it, then "convert to application". Both the site and the app share the same pool.

As long as I call a page of the app (a .aspx) directly through browser address, it works just fine. In addition, the app pages have non-restricted access to the hosting site's files.

But if I call such a page from a .htm page on the site (a non-app page), ASP.NET Event 1310, Event Code 3006, and in the Request information section, User: Is authenticated: False.

My guess was the account IIS uses to access a .aspx page directly is different from the account the web site uses to call such a page from one its own .htm pages.

How can I fix this? (no experience with such issues) Server is 2019.

ASP.NET Event 1310, Event Code 3006, User: Is authenticated: False

Web development includes all aspects of presenting content on intranets and the Internet, including delivery development, protocols, languages and standards, server software, browser clients, databases and multimedia generation.

Web Development

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications

ASP.NET

Web applications are systems that run in browsers that perform functions normally associated with other client-based programs. One of the most commonly used web applications is email; instead of downloading individual emails to a local machine, the data is shown through a website. Other examples of web applications are collaborative systems like a wiki or an online game.

Web Applications

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.