So… here is what I found.
Apparently the Breeze Plugin now requires that the Header in the HTTP communication contain a “User-Agent” header. Up to the latest releases, that was NOT required. So when my application was accessing it Breeze was throwing out a 500 Error. As soon as I added in that header, all was well.
I did however also run into some issues with the GZip compression being active. Either that wasn’t working before or something changed so that my application cannot “read” the streamed data. Not sure what changed, but I had to turn off Gzip compression in order to get my application to work with it. Again, this worked just fine (with GZip turned on) up until the most recent Breeze release.
Hopefully that info helps someone else in debugging strange errors appearing that were never there before ??
