IE has an arbitrary url length limit (2048 bytes, IIRC), so many server
side libraries dont bother to look at more chars than that. can you POST
the data instead?

can you run the server not under ssl to test?

allan

On Fri, Nov 18, 2005, Tim McDonald <tmc_programmer_at_yahoo.com> said:

> I am sending a very large post, 17447 chars URL
> encoded, to a website, and am getting "<h1>Url Too
> Long</h1>" as the response. I am using the .NET
> bindings. Because the posts are done using a SSL
> connection, I am having trouble telling if this
> response is from the library or from the web server.
> The following is a snippet of the code.
> //*************************************************
> easy.SetOpt(CURLoption.CURLOPT_POSTFIELDSIZE_LARGE,(long)s10.Length);
> easy.SetOpt(CURLoption.CURLOPT_URL, s10);
>
> easy.Perform();
> easy.Cleanup();
> Curl.GlobalCleanup();
> //*************************************************
>
> I should also probably metion that this post is being
> processed by an .aspx page, and that other than this
> one page, I haven't had any trouble.
>
> Thanks in advance Timothy McDoanld
>
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
>

-- 
m. allan noah
IT Director, TfHS.net
ph# (804) 355-5489
tf# (866) 724-9722
fx# (804) 355-0477