K
Keith Patrick
I've got an app that does a ton of Response.Redirect's to bring up various
pages. Due to some printer-friendly stuff we use, the URLs all have to pass
their data in via the querystring. However, we're hitting problems where
the URL becomes too long, so now I'm trying to convert all the
querystring-based URLs to simple ones where the key/value pairs are placed
in the header rather than in the URL. I have it working via
WebClient.UploadValues, and I had an attempt via streaming data manually
to/from HttpWebRequests/Responses, but the issue I run into every time is
that my resulting page is the login page, since the new calls fail forms
authentication. Is there some way to transfer the session/authentication
data to the client or response/request, or should I find a new means for
converting to POST?
pages. Due to some printer-friendly stuff we use, the URLs all have to pass
their data in via the querystring. However, we're hitting problems where
the URL becomes too long, so now I'm trying to convert all the
querystring-based URLs to simple ones where the key/value pairs are placed
in the header rather than in the URL. I have it working via
WebClient.UploadValues, and I had an attempt via streaming data manually
to/from HttpWebRequests/Responses, but the issue I run into every time is
that my resulting page is the login page, since the new calls fail forms
authentication. Is there some way to transfer the session/authentication
data to the client or response/request, or should I find a new means for
converting to POST?