not requiring default.avfp by changing web.config

Topics: Developer Forum, Project Management Forum, User Forum
Dec 18, 2014 at 3:35 PM
Edited Dec 18, 2014 at 3:47 PM
If you don't want to have to type in default.avfp, the handlers section of avfp should look like this (if using avfp scripts):

   <add verb="*" path="*.avfp" 

*take out the other handler

Do the direct opposite for a default Controller method:

take out the above handler and leave the one in for Path ="*"

If you want to have default handling you just can't have both handlers in web.config.

Problem with making .avfp the default document: Looks like the web.config
has to have one or the other, either .avfp or .*, not both, in order to make a
default document (or controller method).

This also works in the web root, as long as that application pool is set up for
32 bit operation.

In my tests, .avfp works well this way. However, a default controller method is
returning 'false' to the browser from somewhere in the controller parent code.
I believe it will work but we need to track down exactly what it's doing.

So, default .avfp pages and controller methods should work from any virtual
directory, even the web root.