Windows 2008 - IIS 7.0 - CGI / Webbatch.exe downloads instead of Execute

[usheretov]

Hello - i just installed Webbatch on Win2k8 IIS 7 - and followed all the instructions, - and so I'm not sure what I'm missing. The problem is he webbatch.exe downloads when testing:




http://www.yourmachine.com/webcgi/webbatch.exe?stones/stones.web   


this only causes the EXE to download




http://www.yourmachine.com//webcgi/webbatch.exe?stones/stones.web   


this works fine  notice the // before the webcgi


????

[td]

Windows 2008?

Generally, this is the result of misconfiguring IIS. One common problem is setting the CGI/FastCGI Handler Mappings access to "script" instead of "execute". There are several other settings that can cause the problem. It takes some time and patience to identify this type of problem.

[usheretov]

  everything works -except the natural URL is not working - it only works if i add a // for the cgi directory like this:

http://www.yourmachine.com//webcgi/webbatch.exe?stones/stones.web



this works fine  notice the // before the webcgi

[td]

If you look at any of our WinBatch sites hosting WebBatch, you will notice that the double forward-slash is not necessary. It is still likely that it is a configuration problem of some kind. What that might be I have no idea because it has never been mentioned before.  According to the URI RFC every slash has a significance which leads to the idea that something is not set correctly.

[usheretov]

uff - sorry - i got it to work - i didnt configure DNS - so i added my domain in aws route53 - pointed to my host ip and it works fine.  the reason // was working was because in IIS - under site bindings there is  by default host name is blank - that listens on port 80 so // is technically that reference so that the virtual drive will work properly. anyway - in the documentation - you can add that internet DNS needs to be setup to match the bindings. for security the default "blank" host name is not a good idea to keep

[td]

It makes sense. The double forward-slash is telling browsers to reparse from the beginning because it indicates a new domain. (It seems obvious once someone else figured it out.) And nice work figuring it out.