IIS6 problem with querystrings

We have a large web application originally written on WIN2000/IIS5. The
application uses CHR(1) thru CHR(15) as delimiters in the querystrings. IIS5
allowed this but IIS6 does not. I realize that this is a bad coding
practice, but the application is already written and would require
significant effort to fix. Is there a way to force IIS6 to allow the CHR()
characters in querystrings like IIS5 does? This behavior would be acceptable
since the application runs scrictly on a local network.
--
GreggG

Re: IIS6 problem with querystrings

what's the exact error? have you look at the httperr ?
you can try tweak the http.sys setting if it's due to its policy.

Http.sys registry settings for IIS
http://support.microsoft.com/Default.aspx?id=820129


--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"GreggG" wrote in message
news:1A4EC8EB-60B5-4A15-801C-DF6C4050D04E@microsoft.com...
> We have a large web application originally written on WIN2000/IIS5. The
> application uses CHR(1) thru CHR(15) as delimiters in the querystrings.
> IIS5
> allowed this but IIS6 does not. I realize that this is a bad coding
> practice, but the application is already written and would require
> significant effort to fix. Is there a way to force IIS6 to allow the
> CHR()
> characters in querystrings like IIS5 does? This behavior would be
> acceptable
> since the application runs scrictly on a local network.
> --
> GreggG

Re: IIS6 problem with querystrings

Thanks for the reply. We tried the setting for AllowRestrictedChars and it
did not work. As described, it works with hex-escaped characters. These are
the actual non-printing characters, chr(1) thru chr(15). I believe that the
error is "Bad Request", but I am not able to test it at this point in time.

--
GreggG


"Bernard Cheah [MVP]" wrote:

> what's the exact error? have you look at the httperr ?
> you can try tweak the http.sys setting if it's due to its policy.
>
> Http.sys registry settings for IIS
> http://support.microsoft.com/Default.aspx?id=820129
>
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://msmvps.com/blogs/bernard/
>
>
> "GreggG" wrote in message
> news:1A4EC8EB-60B5-4A15-801C-DF6C4050D04E@microsoft.com...
> > We have a large web application originally written on WIN2000/IIS5. The
> > application uses CHR(1) thru CHR(15) as delimiters in the querystrings.
> > IIS5
> > allowed this but IIS6 does not. I realize that this is a bad coding
> > practice, but the application is already written and would require
> > significant effort to fix. Is there a way to force IIS6 to allow the
> > CHR()
> > characters in querystrings like IIS5 does? This behavior would be
> > acceptable
> > since the application runs scrictly on a local network.
> > --
> > GreggG
>
>
>

Re: IIS6 problem with querystrings

After some additional searching, I found a post that refers to a new setting
in 2003 SP1 called AllowUnEscapedRestrictedChars. That sounds like the
solution that will work for us.

--
GreggG


"Bernard Cheah [MVP]" wrote:

> what's the exact error? have you look at the httperr ?
> you can try tweak the http.sys setting if it's due to its policy.
>
> Http.sys registry settings for IIS
> http://support.microsoft.com/Default.aspx?id=820129
>
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://msmvps.com/blogs/bernard/
>
>
> "GreggG" wrote in message
> news:1A4EC8EB-60B5-4A15-801C-DF6C4050D04E@microsoft.com...
> > We have a large web application originally written on WIN2000/IIS5. The
> > application uses CHR(1) thru CHR(15) as delimiters in the querystrings.
> > IIS5
> > allowed this but IIS6 does not. I realize that this is a bad coding
> > practice, but the application is already written and would require
> > significant effort to fix. Is there a way to force IIS6 to allow the
> > CHR()
> > characters in querystrings like IIS5 does? This behavior would be
> > acceptable
> > since the application runs scrictly on a local network.
> > --
> > GreggG
>
>
>

Re: IIS6 problem with querystrings

:) you need to base on the reason phrase in httperr log to find out what is
blocking it.

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"GreggG" wrote in message
news:D7901273-E731-4D77-99F9-A4DD6F110A32@microsoft.com...
> After some additional searching, I found a post that refers to a new
> setting
> in 2003 SP1 called AllowUnEscapedRestrictedChars. That sounds like the
> solution that will work for us.
>
> --
> GreggG
>
>
> "Bernard Cheah [MVP]" wrote:
>
>> what's the exact error? have you look at the httperr ?
>> you can try tweak the http.sys setting if it's due to its policy.
>>
>> Http.sys registry settings for IIS
>> http://support.microsoft.com/Default.aspx?id=820129
>>
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis.net/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "GreggG" wrote in message
>> news:1A4EC8EB-60B5-4A15-801C-DF6C4050D04E@microsoft.com...
>> > We have a large web application originally written on WIN2000/IIS5.
>> > The
>> > application uses CHR(1) thru CHR(15) as delimiters in the querystrings.
>> > IIS5
>> > allowed this but IIS6 does not. I realize that this is a bad coding
>> > practice, but the application is already written and would require
>> > significant effort to fix. Is there a way to force IIS6 to allow the
>> > CHR()
>> > characters in querystrings like IIS5 does? This behavior would be
>> > acceptable
>> > since the application runs scrictly on a local network.
>> > --
>> > GreggG
>>
>>
>>