Newbe: Redirect and QueryString HELP PLZ

[EDOnLine]

We have a page which, after inserting a record ID to our database via stored
proceedure, redirects the user to a URL on a thrid party site which as
passed to that page via QueryString. In other words this is an intermediate
counting page between the user's click and their arrival at their selected
URL.

This seems to be working just fine - except when long URLs are passed to the
page. In that case we're getting "file not found" errors on the thrid party
sites and which make it appear that the URL is being cut off somewhere in
the process. I've checked the source in the browser on our end and the <a
href> tag that the user clicks on is being created correctly.

Is there a limit to the length of QueryString or the URL passed to Redirect?

By long URLs I mean roughly 100 to 150 characters. I had understood that
QueryString would handle at least a couple of thousand.

Any ideas on how to make this work?

Thanks in advance!

[Joerg Jooss]

Thus wrote EDOnLine,

We have a page which, after inserting a record ID to our database via
stored proceedure, redirects the user to a URL on a thrid party site
which as passed to that page via QueryString. In other words this is
an intermediate counting page between the user's click and their
arrival at their selected URL.

This seems to be working just fine - except when long URLs are passed
to the page. In that case we're getting "file not found" errors on
the thrid party sites and which make it appear that the URL is being
cut off somewhere in the process. I've checked the source in the
browser on our end and the <a
href>> tag that the user clicks on is being created correctly.
href>> Is there a limit to the length of QueryString or the URL passed to
Redirect?

By long URLs I mean roughly 100 to 150 characters. I had understood
that QueryString would handle at least a couple of thousand.

There's no standardized maximum URL legth, but assume 2 kB for all practical
purposes. I guess you'll have to check the URLs logged on the third party's
site to find out whether they're being truncated.

Cheers,
--
Joerg Jooss
ne********@joer gjooss.de

[EDOnLine]

What is the best method for doing this?

Thanks

"EDOnLine" <ed*******@yaho oX.com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

We have a page which, after inserting a record ID to our database via
stored proceedure, redirects the user to a URL on a thrid party site which
as passed to that page via QueryString. In other words this is an
intermediate counting page between the user's click and their arrival at
their selected URL.

This seems to be working just fine - except when long URLs are passed to
the page. In that case we're getting "file not found" errors on the thrid
party sites and which make it appear that the URL is being cut off
somewhere in the process. I've checked the source in the browser on our
end and the <a href> tag that the user clicks on is being created
correctly.

Is there a limit to the length of QueryString or the URL passed to
Redirect?

By long URLs I mean roughly 100 to 150 characters. I had understood that
QueryString would handle at least a couple of thousand.

Any ideas on how to make this work?

Thanks in advance!

[intrader]

On Mon, 27 Mar 2006 14:12:40 -0600, EDOnLine wrote:

We have a page which, after inserting a record ID to our database via stored
proceedure, redirects the user to a URL on a thrid party site which as
passed to that page via QueryString. In other words this is an intermediate
counting page between the user's click and their arrival at their selected
URL.

This seems to be working just fine - except when long URLs are passed to the
page. In that case we're getting "file not found" errors on the thrid party
sites and which make it appear that the URL is being cut off somewhere in
the process. I've checked the source in the browser on our end and the <a
href> tag that the user clicks on is being created correctly.

Is there a limit to the length of QueryString or the URL passed to Redirect?

By long URLs I mean roughly 100 to 150 characters. I had understood that
QueryString would handle at least a couple of thousand.

Any ideas on how to make this work?

Thanks in advance!

This is a guess, as the limit on the QueryString is around 3K.
However, if the site you are accessing is using this long url to generate
a file name, I filename may have a different limit.

[EDOnLine]

Never mind. I had forgot to use Server.UrlEncod e to build my link.

Working great now.

"EDOnLine" <ed*******@yaho oX.com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

We have a page which, after inserting a record ID to our database via
stored proceedure, redirects the user to a URL on a thrid party site which
as passed to that page via QueryString. In other words this is an
intermediate counting page between the user's click and their arrival at
their selected URL.

This seems to be working just fine - except when long URLs are passed to
the page. In that case we're getting "file not found" errors on the thrid
party sites and which make it appear that the URL is being cut off
somewhere in the process. I've checked the source in the browser on our
end and the <a href> tag that the user clicks on is being created
correctly.

Is there a limit to the length of QueryString or the URL passed to
Redirect?

By long URLs I mean roughly 100 to 150 characters. I had understood that
QueryString would handle at least a couple of thousand.

Any ideas on how to make this work?

Thanks in advance!