<export> and IIS7

[aitchon]

I'm trying to use <export> to save a variable across a script, and it works fine in IIS6, but when I run the script in IIS7, I get a '404 - File or directory not found' error. It seems IIS7 is picky about the the path. Do you know of any settings that I can change that would fix this? Here's a test script that produces the error:

<script language=vortex>
<timeout=-1></timeout>
<export $custid>

<a name=main>
<$custid=1>
<form method=post action=$url/listbooks.html>
<table>
<tr><td align=right>Author:<td></td> <td><input size=40 name=qAuthor value=$qAuthor></td><tr>
<tr><td align=right>Title:<td></td> <td><input size=40 name=qTitle value=$qTitle></td><tr>
<tr><td align=right>Subject:<td></td> <td><input size=40 name=qSubject value=$qSubject></td><tr>
<tr><td align=right>Category:<td></td><td><select name=qCategory><options $catlist $qCategory $catlist></select><input type=submit></td><tr>
</table>
</form>
</a>

<a name=listbooks PUBLIC>
$qAuthor
</a>

</script>

[jason112]

What's the full URL for the original page, and the page that's linked to that gives the 404?

[aitchon]

http://192.168.10.15/scripts/texis.exe/testform

http://192.168.10.15/scripts/texis.exe/ ... books.html

[jason112]

For future archeologists mining the message board, the problem was solved by turning off IIS's "prevent double escaping" protection. Our /+ state information syntax in the URL triggers it, even though it's valid.

This KB article discusses how to change it:
http://support.microsoft.com/kb/942076/