I am returning 666 as the respone status code to reverse proxy when
there is a problem with the request. IIS 5.x sends this 666 as it is to
reverseproxy where in IIS 6.0 this 666 response code is being send as 200.
Please help, if any changes required in configuration of IIS 6.0.
Hello,
You need to tell us more. How do you return this status code? It is much
faster to debug this than looking for the differences between IIS 5.x and
IIS 6.0.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Suresh Babu wrote:
>I am returning 666 as the respone status code to reverse proxy when
>there is a problem with the request. IIS 5.x sends this 666 as it is to
>reverseproxy where in IIS 6.0 this 666 response code is being send as 200.
>Please help, if any changes required in configuration of IIS 6.0.
Kristofer,
Here is the code.
Select case LCase(mstrAction)
Case "submit"
gwebPage.Controls.LoadRequest
gwebPage.Controls.Validate
gstrErrorsXML = gcolErrors.XML
If CBool(mbobLogon.UserLogon(gcolSessionInfo.XML, gstrErrorsXML,
gwebPage.Controls(cInputUsername).Value,
gwebPage.Controls(cInputPassword).Value,clng(gwebPage.Contro ls(cInputCCCoord).Value), gwebPage.Controls(cInputCCValue).Value, blnGenerateNewCC)) Then
gwebsession("LogonType") = "CL"
gwebsession.saveState
Response.Clear
'Response.Cookies("SID") = ""
Response.Status = 666
Select Case CStr(Ucase(Request.ServerVariables("server_name")))
Case "LOCALHOST", "10.131.118.59" ' Working on local machine or
directly on the dev. IIS server
Response.Redirect
"../ebanking/security/logon.asp?userid=" &
Trim(gwebPage.Controls(cInputUsername).Value)
Case Else ' Accessing the site via a proxy
Response.End
End Select
End If
gcolErrors.XML = gstrErrorsXML
End Select
"Kristofer Gafvert" wrote:
> Hello,
>
> You need to tell us more. How do you return this status code? It is much
> faster to debug this than looking for the differences between IIS 5.x and
> IIS 6.0.
>
>
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Suresh Babu wrote:
>
> >I am returning 666 as the respone status code to reverse proxy when
> >there is a problem with the request. IIS 5.x sends this 666 as it is to
> >reverseproxy where in IIS 6.0 this 666 response code is being send as 200.
> >Please help, if any changes required in configuration of IIS 6.0.
>
Hello,
What i can understand is that the code that excutes is the following:
Response.Status = 666
Response.End
I tried to put that into an asp file and excute it on a Windows Server
2003 machine running IIS 6, and it returns with the status code 666.
So you must have something else that is changing this behavior, or your
code is not correct.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Suresh Babu wrote:
>Kristofer,
>
> Here is the code.
>
>
>Select case LCase(mstrAction)
> Case "submit"
> gwebPage.Controls.LoadRequest
> gwebPage.Controls.Validate
>
> gstrErrorsXML = gcolErrors.XML
>
> If CBool(mbobLogon.UserLogon(gcolSessionInfo.XML, gstrErrorsXML,
>gwebPage.Controls(cInputUsername).Value,
>gwebPage.Controls(cInputPassword).Value,clng(gwebPage.Contr ols(cInputCCCoord).Value),
>gwebPage.Controls(cInputCCValue).Value, blnGenerateNewCC)) Then
>
> gwebsession("LogonType") = "CL"
>
> gwebsession.saveState
> Response.Clear
> 'Response.Cookies("SID") = ""
> Response.Status = 666
>
> Select Case CStr(Ucase(Request.ServerVariables("server_name")))
> Case "LOCALHOST", "10.131.118.59" ' Working on local machine or
>directly on the dev. IIS server
> Response.Redirect
>"../ebanking/security/logon.asp?userid=" &
>Trim(gwebPage.Controls(cInputUsername).Value)
> Case Else ' Accessing the site via a proxy
> Response.End
> End Select
>
> End If
>
> gcolErrors.XML = gstrErrorsXML
>End Select
>"Kristofer Gafvert" wrote:
>
>>Hello,
>>
>>You need to tell us more. How do you return this status code? It is much
>>faster to debug this than looking for the differences between IIS 5.x and
>>IIS 6.0.
>>
>>
>>
>>--
>>Regards,
>>Kristofer Gafvert
>>http://www.gafvert.info/iis/ - IIS Related Info
>>
>>
>>Suresh Babu wrote:
>>
>>>I am returning 666 as the respone status code to reverse proxy when
>>>there is a problem with the request. IIS 5.x sends this 666 as it is to
>>>reverseproxy where in IIS 6.0 this 666 response code is being send as
>>>200.
>>>Please help, if any changes required in configuration of IIS 6.0.
>>