> >François has written a Universal Plug and Play component
>
> Yeah I tried it first and the device does not respond. It needs a
> "discover" verb to respond. Windows uses "All", IIRC.
Typical Microsoft, half baked APIs. Probably explains why it does not
find all my devices, although I do
Hello,
>François has written a Universal Plug and Play component
Yeah I tried it first and the device does not respond. It needs a "discover"
verb to respond. Windows uses "All", IIRC.
As with the HTTP, "does not fully implement all the requirements." applies
here as well.
Thanks for your
> I switched to a TWSocket and sent the complete post URL, parameters and
XML data in one send
> and the server responded without error. So, the header data the THttpCli
component was adding
> to the XML document was not allowed by the server. Only the XML data.
This makes me thinking your
It would be interesting to know what header(s) in particular is/are
causing the problem. You may use the OnBeforeHeaderSend event to remove
any of the headers, before the headers are sent.
Or just temporary comment the code related to each of the header lines
being sent, under the
org>
Subject: Re: [twsocket] THttpCli and XML...
> I must be doing something wrong.
>
Are you setting the THttpCli.ContentTypePost property to the Content-Type
(in your case "application/xml", I suppose) the server is expecting ?
http://stackoverflow.com/questions/3272534/what-conte
Hello,
Version 7.25
For the first time I need to send an XML document to the server.
I setup the URL for all the data.
I put the XML document in a stream and set the index to 0.
I call PostASync.
Looking at Wireshark the URL data is all there and correct.
The XML has stuff added to the front
