> >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 tend
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 time
> > and I conclude that is doesn't [fully] support HTTP.
>
> I concur. It is a hybrid. It requires all the formatting of HTTP
> ("Gets" to the device via THttpCli work without error) and XML
> but, does not fully implement all the requirements.
In which most of the capabilities of THttpCli are
Hello,
> and I conclude that is doesn't [fully] support HTTP.
I concur. It is a hybrid. It requires all the formatting of HTTP ("Gets" to
the device via THttpCli work without error) and XML but, does not fully
implement all the requirements.
It uses SSDP and UDP to be discovered and how it is im
> 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 server
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 OverbyteIcsH
Hi,
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.
Joy!
Thanks for your time,
Mark
Hello,
Thanks for the responses.
> My sData is not XML but this should not make big difference.
Yeah I thought so to but, it appears the device does not like the headers
added by THttpCli.
> Are you setting the THttpCli.ContentTypePost property to
Yes, same as above.
I am about to shift to
I use
ContentTypePost = application/x-www-form-urlencoded
I don't use XML however.
Jarek Karciarz
-Original Message-
From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of RTT
Sent: Sunday, March 6, 2016 9:12 PM
To: ICS support mailing
Subject: Re: [twsocket] THt
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-content-type-value-should-i-send-for-my-xml-sitemap
--
To unsubs
...@lists.elists.org] On Behalf Of zayin
Sent: Sunday, March 6, 2016 7:33 PM
To: twsoc...@elists.org
Subject: [twsocket] THttpCli and XML...
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 a
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 whi
12 matches
Mail list logo
