Error HTTP 403.18 - Forbidden jar files

Jesus Obiang 1 Reputation point
2021-09-09T17:33:07.57+00:00

Hi all,

I have an application build in ASPNET Core. It is hosted on IIS 6. the application works except when trying to access .js files. For example, I have a dropdown component, and when I try to get a value, it is impossible, the drop-down does not get anything. if I put in the URL the path of the jar file I get the error: Error HTTP 403.18 - Forbidden.
I think that my configuration of IIS is correct, the user IIS_USER has all permissions. The authentication mode is Anonymous.

Thank you very much for your help.

Regards,

Internet Information Services
ASP.NET Core
ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,291 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sam Wu-MSFT 7,131 Reputation points Microsoft Vendor
    2021-09-10T02:12:34.493+00:00

    @Jesus Obiang

    There are many reasons for 403.18 error:

    • An ISAPI filter or custom module changed the URL to run in a different application pool than the original URL.
    • An ISAPI extension (or custom module) used ExecuteURL (or ExecuteRequest) to run in a different application pool than the original URL.
    • You have a custom error page that is located in one application pool but is referenced by a Web site in another application pool. When the URL is processed, it is determined by IIS that that it should have been processed in the first application pool, not the other pool.
    • The Web site has multiple applications configured. The application this request is configured to run in is set to run in an application pool that does not exist.

    Things you can try:

    • If you have an application that is trying to process a URL in another application pool (such as trying to process a custom error), ensure that they both run in the same application pool if appropriate.
    • If you are trying to process a custom error URL that is located in another application pool, enable the custom errors Redirect feature.
    • Verify that the application pool for the application exists.
    • Create a tracing rule to track failed requests for this HTTP status code and see if ExecuteURL is being called.

    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments