Re: blank response from curl when posting form data



I forgot to mention: they are properly encoded with urlencode. I
checked against Firefox headers. As soon as I make those strings small,
under 800 characters, everything works. This is checked against several
webhosts too: Godaddy, Bluehost, Network Solutions, and my own server,
all return the same error:

cURL ERROR #56: Received problem 2 in the chunky parser at 186 in
/home/public_html/poster.php
I have this at line 186:
if(curl_errno($ch) > 0) echo "<p style='color: red'><b>cURL ERROR
#".curl_errno($ch).": ".curl_error($ch)." at ".__LINE__." in
".__FILE__."</b></p>";

If I take that line out, I get a blank response from the Post.
It only works without a hitch on Marblehost. So I'm thinking it may be
a config issue, but I need a way to make it work on my computer. This
is rather intriguing. I tried passing the post data in strings, arrays
and directly with the same result. I have also tried passing it a file,
which, I read, handles buffering better (doing that I'm returned the
blank form again, which I initially get on the previous step with a
simple curl call to that url without a post), but I am not sure I did
file passing correctly. Any example on how to do this correctly, as
well as any other advice would be really appreciated.

.



Relevant Pages

  • Re: stored procedure
    ... characters - make sure it is enough characters for the strings you are ... passing. ... > How can I make the server name a variable and an input field to the sp? ...
    (microsoft.public.sqlserver.programming)
  • Re: Why R6RS is controversial
    ... the semantics of the language, ... behavior of grapheme-cluster characters under most linguistic ... as the strings grow longer. ... Normalization is hideously complicated, and may require many ...
    (comp.lang.scheme)
  • Re: Unicode LISP??
    ... I'm not experienced with Common Lisp library, ... terms of strings rather than characters. ... have their representation upgraded if they are updated in place. ...
    (comp.lang.lisp)
  • Re: not quite 1252
    ... The kill_gremlins function is intended to fix Unicode strings that have been obtained by decoding 8-bit strings using 'latin1' instead of 'cp1252'. ... In fact it wasn't, it was UTF-8 like Sergei wrote, but it was easy to convert it to cp1252, no problem. ... characters to documents marked up as ISO 8859-1 or other encodings. ...
    (comp.lang.python)
  • Re: How to check variables for uniqueness ?
    ... FI in English typography), so the correct uppercase version of those ... characters is the sequence SS. ... So you at least agree with me that it should be consistent with toUpperCase -- all strings should have a single canonical toUpperCase, a single canonical toLowerCase, both should define equivalence classes on the mixed-case input strings, these should be the SAME equivalence class, and equalsIgnoreCase should implement and embody the corresponding equivalence relation. ... The version that doesn't shouldn't surprise English speakers; the version that does shouldn't surprise anyone familiar with its locale-specific behavior for the locale actually used. ...
    (comp.lang.java.programmer)