Re: [twsocket] header too long HTTP_MIME_TOO_LONG

2009-07-16 Thread wayne forrest
I will try my best to describe the problem I am experiencing a bit better;

My PHP side I have this:

?php
session_start();
$a_longString1 = verylong1;
$a_longString2 = verylong2
header(xx: xx=$a_longString1);
header(yy: yy=$a_longString2);
?


On Dlephi side I have this:

var
 aString1,aString2 : String;
begin
  aString1 := HttpCli1.RcvdHeader.Values[xx: xx'];
  aString2 := HttpCli1.RcvdHeader.Values[yy: yy'];


aLongString1 is very long, and using the document/content is not an option
in my case;
and this would require some parsing.

I am not sure how one should pass the data from PHP to Delphi;

Should I be setting some HTTP HEADERS on the PHP SIDE, or maybe some
setting I can make to the APACHE server to get past this ERROR.

Maybe I must specify some MIME TYPE? or is this done by the APACHE SERVER ?

I used WireShark to get the HTTP_MIME_TOO_LONG error by watching the
network traffic.

I did not receive any error on the APACHE server nor on the Delphi side;
I have also noticed that as soon as the data becomes too large, then no data
is returned from
the PHP at all;

Any ideas are welcome please.



$alist does hold a long list of SQL data.
?php
session_start();
header(SQL_RESULTS: SQL_RESULTS=$alist);
?


On Tue, Jul 14, 2009 at 5:22 PM, Francois PIETTE
francois.pie...@skynet.bewrote:

 I am receiving an error: header too long HTTP_MIME_TOO_LONG
 when I call my php file, from HttpCli,
 *How shoud one I get the vars from php?*


 Not sure about what you mean by this sentence...

  I think that there is some kind of limit in the amount of data that can
 fit
 into the header.
 $alist does hold a long list of SQL data.
 ?php
 session_start();
 header(SQL_RESULTS: SQL_RESULTS=$alist);
 ?


 Why would you send your SQL data in the header ? You should probably send
 it in the document.

 --
 francois.pie...@overbyte.be
 The author of the freeware multi-tier middleware MidWare
 The author of the freeware Internet Component Suite (ICS)
 http://www.overbyte.be

 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




-- 
C: 076 337 4368
T: 021 880 2037
F: 021 880 2530
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] header too long HTTP_MIME_TOO_LONG

2009-07-14 Thread Francois PIETTE

I am receiving an error: header too long HTTP_MIME_TOO_LONG
when I call my php file, from HttpCli,
*How shoud one I get the vars from php?*


Not sure about what you mean by this sentence...

I think that there is some kind of limit in the amount of data that can 
fit

into the header.
$alist does hold a long list of SQL data.
?php
session_start();
header(SQL_RESULTS: SQL_RESULTS=$alist);
?


Why would you send your SQL data in the header ? You should probably send it 
in the document.


--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be