Hi Alberto,
Please, please, please tell me you are not planning to have an API service on an insecure connection? I'm hoping you'll say it'll definitely be secure, then I won't have to explode in your direction over your poor security habits...
Secondly, there's quite a lot wrong here. I presume you've "rolled your own" procedure here rather than using the NetWebServiceMethod? Alas if you have you've still got a few corrections to make.
Probably a good way for you to see what is going wrong is just to run the NetDemo app, WebClient procedure, and enter that URL you'll see the result from the server. Compare that to say
https://www.capesoft.com/CapesoftAccessoriesRSSFeed.xml (or any response from a NetWebServiceMethod API).
You'll see your reply lacks the HTTP header, and at the same time includes a line at the top,
<!DOCTYPE html>
which has no meaning.
I hope this gets you going in the right direction...
cheers
Bruce