From: Daniel S. <da...@er...> - 2005-09-16 18:09:46
|
yaws 1.57, solaris x86 I have a strange question, and this might be only because I am illiterate in html / xml :) I have an income XML request POST or GET and when responding to this with the lines: <erl> {content, "text/xml", <<"XML Response Data">>} </erl> it works perfectly the first time it gets invoked. However, when the second xml request is sent - it just "disappears". The sender of the XML can see the data being sent - but the response just times out. The questions now are: 1. Am I not closing off my response correctly so that YAWS does not know that I have stopped responding and can be ready for the next request. 2. If I want to force the connection to close by adding the Header: close command :) how would I add that. all the variations of {html, [{header, close} ... ]} etc does not seem to work. 3. Am I missing something obvious? -- Daniel H Schutte Mobile: +27 84 468 3138 Office: +27 11 675 2643 The more laws and order are made prominent, the more thieves and robbers there will be. -- Lao Tsu |
From: Claes W. <kl...@ta...> - 2005-09-18 16:06:31
|
Daniel Schutte wrote: > yaws 1.57, solaris x86 > > I have a strange question, and this might be only because I am illiterate in > html / xml :) > > I have an income XML request POST or GET and when responding to this with the > lines: > > <erl> > {content, "text/xml", <<"XML Response Data">>} > </erl> > You need to have an out/1 function defined inside the <erl> ... </erl> block as in: <erl> out(A) -> {content, "text/xml", <<"Hello there">>}. </erl> /klacke |
From: Claes W. <kl...@hy...> - 2005-09-18 16:11:40
Attachments:
klacke.vcf
|
Daniel Schutte wrote: > 2. If I want to force the connection to close by adding the Header: close > command :) how would I add that. all the variations of {html, [{header, > close} ... ]} etc does not seem to work. <erl> out(A) -> [ {content, "text/xml", <<"Hello there">>}, {header, {connection, "close"}} ]. </erl> |