I cannot truly help, but I do use IIS and have found that it can be cantankerous. I would suggest simply trying to get a static file from web2py then you can work on the IIS settings to allow certain types of files that it might be blocking. The 404 on a new IIS installation simply means you haven't got the plumbing right yet. I recently added an ashx file type and found that there were two locations (because we were following best security practices list we had gotten a hold of) that I had to find and modify to allow this new extension type. This of course took hours.
Hopefully I spark something in your brain that makes you check and find the answer. Good luck. On Thursday, April 6, 2017 at 6:48:44 PM UTC-7, weheh wrote: > > I've now compared my installation against a known good installation. All > the various parameters and installed routines are the same, but still > getting the 404 message. Anybody have any thoughts about what it might be > or what I should be looking at? > > On Thursday, April 6, 2017 at 3:12:51 PM UTC-6, weheh wrote: >> >> Have been struggling with web2py behind IIS installation on AWS for a >> couple of days now and getting nowhere. The best I am able to produce is a >> 404 error message. I've tried two completely clean installations from >> scratch, followed the web2py book documentation to the letter, and still no >> go. Any ideas what I should be checking? >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
