So I did ultimately figure out why my code all of the sudden stopped working when I switched over to HTTPS from regular HTTP. Apparently the two libraries behave differently when sending the body out.? I was using a HTTP GET request in this particular case.? While the HTTP spec doesn't seem to specifically disallow using a body in a GET request, the HTTPS client does not allow for it at all.? Interesting thing though is that the regular HTTP client does allow for it and it works fine.
This would have been a lot easier to find if both of the libraries (HTTP and HTTPS) behaved the same.
Nick
toggle quoted message
Show quoted text
On 4/14/21 7:44 PM, Nick Pepper wrote:
Joe
I appreciate the code, I'll modify mine a bit and see how it works.? Next step is as you said, to roll back to previous databases and see how things go.? I'm assuming that the MC3 worked at some point in history, but maybe I could be wrong as it has always been a bastard.
Nick
On 4/11/21 9:37 PM, Joe wrote:
MC3 has always been a bit of a pain.? You might want to try the code on another control system to rule out the MC3 or the older SW database.? ?I had to do something similar on an RMC3 a month back and didn't have any problems.? I just looked at the code and I have .ContentString inplace of your .ContentBytes and do not use .ContentSource at all.? Not sure it helps, but below is a sample of the code I moved over from http to https for a RainMachine irrigation controller.
