I have found why the restrictions are not being interpreted from the web.config file. I have a global.asax which looks like this:

<object id="LXFramework" runat="server" class="Framework.Framework.App" scope="Application" />

<script runat=server>

    Sub Application_Start(ByVal sender As Object, ByVal e As EventArgs)
        LXFramework.nApplicationMode = 3
        LXFramework.oServer = Server
        LXFramework.Initialize()
    End Sub

    Sub Application_BeginRequest(ByVal sender As Object, ByVal e As EventArgs)
        LXFramework.oRequest = Request
        LXFramework.oResponse = Response
        LXFramework.oServer = Server
        LXFramework.BeginRequest()
    End Sub
    
    Sub Application_EndRequest(ByVal sender As Object, ByVal e As EventArgs)
        LXFramework.oResponse.Write(LXFramework.GetJavascriptMessage)
        LXFramework.EndRequest()
    End Sub

    Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
        LXFramework.LogError()
    End Sub

    Sub Application_PreRequestHandlerExecute(ByVal sender As Object, ByVal e As EventArgs)
        Dim loPage As System.Web.UI.Page = Context.Handler
        LXFramework.oPage = loPage
    End Sub
   
</script>

The way it is now, it will work if I comment the BeginRequest, Error and PreRequestHandlerExecute sections. But, if I use the file as is, this will make global.asax to take over the file, try to interpret it, before web.config has priority. So, basically, my global.asax is conflicting with the web.config file. But, I really need the global.asx file to be as is. Is there a way to have my global.asx to be as is and still have web.config to take priority over the restrictions I will put in the httpHandlers?