Hi,

On a site I am trying to set up a site in COM mode and I get this JS error when loading the login form (the first form) :

The form is displayed, but this error is displayed in the browser :
At the same time the JS is caught in an infinite loop it seems, the page is very unresponsive.
What does this mean please?
.
.
Also, I do not understand how the awscripts_Source folder works in production.
If I remove this folder, which I should on a production server, then I get this JS error :
This results in the form loading, but no JS working.
So, I am not seeing how FiC adapts to not having the _Source folder present.

Thanks
Paul

404 error means that the URL http://192.168.9.16:8080/MethExec.web does not exist. Maybe the .web script-mapped extension is not defined.

awProcess.cawJSinc() uses _Source\ if exe was compiled with DEBUGMODE = .T. (which should never happen) or running from within the VFP IDE. I recommend using xxxProd.update.prg which makes sure to compile the exe with DEBUGMODE = .F. before updating the production server.

Yeah, it does look like there is something wrong with script mapping.
But everything I have looked at seems correct - .wc and .web (xxx) handler mappings on the site and CGI & ISAPI restrictions at the IIS level. The application pool is running under LOCALSYSTEM and NTFS permissions seem correct.

Strangely, it seems that WC sort-of works.
If I navigate to http://localhost:8080/wFormStandardPage.web?awFrm=loginform&nocache=_5N412ZV7M then the page works.
But if I navigate to http://localhost:8080/index.web then I get an error : HTTP Error 404.20 - Not Found and the URL in the browser changes to http://localhost:8080/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/index.web/......
404.20 = Too Many URL Segments
Index.web does exist.

Testing with IE11 and Firefox.

EDIT : insert much swearing here
I have found the problem, but I will post this anyway for other people to learn from.
Once I cleared the cookies and temp files from the browser the mapping started to work and the site is now fine. Sigh.

Paul