Hello

I have a strange problem, I'm using Debitech for a system that handles
payments. And I have this Response.Redirect(https://long address) that is
sent to their server with a long querystring. For some reason
Response.Redirect renders a "Page cannot be displayed" error (and no
asp-error) if it gets abit long, but if I copy that same address into a new
browser and surf to it it works.

Is there some sort of maximum url-length in the IIS of Windows 2003? been
doing response.redirects since -97 so this is abit strange.

Any ideas on this one?
/Lasse

Lasse Edsvik wrote on 24 jul 2007 in
microsoft.public.inetserver.asp.general:
> I have a strange problem, I'm using Debitech for a system that handles
> payments. And I have this Response.Redirect(https://long address) that
> is sent to their server with a long querystring.

ASP Response.Redirect does not send anything to any server,
but sends a header to the browser advising that browser to redirect to
another page perhaps on another server.

> For some reason
> Response.Redirect renders a "Page cannot be displayed" error (and no
> asp-error) if it gets abit long, but if I copy that same address into
> a new browser and surf to it it works.
> Is there some sort of maximum url-length in the IIS of Windows 2003?
> been doing response.redirects since -97 so this is abit strange.

Then you would get an ASP error.

Did you try different browsers?

Did you do a header read?

Try clientside javascript on IE(!!) with this code:

<script type='text/javascript'>
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP");
function getUrlhead(url) {
xmlhttp.open("HEAD", url,false);
xmlhttp.send()
return xmlhttp.getAllResponseHeaders();
};
document.write(getUrlhead('http.........'))
</script>

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)