Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can I cause a redirect in ASP (pre .NET) to carry the Basic Authorization header as the ASP request. We tried using the following code .
response.setHeader( 'Authorization', 'Basic ' + strAuth ); response.sendRedirect( src ); response.flushBuffer(); The header is set on the response of the .asp, but not passed on to the request to the new page. Is there a way to make sure the Authorization header is attached to the resulting request?
Are you redirecting to another ASP ‘classic’ page in the same site? If so, you’re better off storing the auth string in a Session variable and/or using Server.Transfer. Server.Transfer will transfer execution to another ASP script, which will then have access to the Request object of the calling page.
Also… response.setHeader? In classic pre-.NET ASP? Classic ASP uses response.addheader and response.redirect, not response.setHeader and response.sendRedirect.
Maybe you’re using On Error Resume next and you’re not seeing the errors the code is actually generating. Because that code will not run.