The last time I updated my DynDNS addresses my script failed. Did you change the content-type of your update response from 'text/html' to '*/*' ? Now the response is a byte array instead a string.
Hi SamLowry,
Yes, that’s right. I believe we nowhere give any guarantees about the content type.
Nevertheless, I added a fix here. It may take a few days before we roll it out. (You can follow the PR on GitHub to get notified.)
Stay secure,
Peter
Hi Peter,
it wasn’t much of a problem, it was just unexpected. But I think it’s a good idea to change it back to ‘text / plain’. Thanks.
Stay consistent 
,
Sam
Hi Peter,
I can confirm that the content-type is now ‘text/plain’.
It is common and recommended to also include a charset, but why follow a recommendation from the W3C?
https://www.w3.org/International/articles/http-charset/index.en
Regards,
Sam
Hi Sam,
Declaring the charset could be a nice addition to deSEC. I’m looking forward to your pull request with the appropriate changes at GitHub to improve our free open-source service further! 
Best,
Nils
1 Like
Hello Nils,
I didn’t know it was such a difficult task. If you can’t do it, I definitely won’t. In the meantime I am happy that an answer is generated at all.
I hope you find more capable contributors to your project.
All the best,
Sam
Hi Sam,
To clear up the confusion, we would be able to do it The thing is that our todo list is very long, and especially for the easier tasks, we very much appreciate community contributions. But don’t worry, it’s always good to get input here; don’t feel obliged!
Stay secure,
Peter
1 Like