Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
C0D4668946y@JackToolsNet that was my first thought, but it literally returned x, that’s not a place holder. So if it is rate limited it’s a shitty way of saying it.
-
C0D4668946y
Related Rants
-
m1guelpf24I have to admit I didn't expect that...
-
ChipND7I have an array of 1037 records. The soap service only accepts 100 at a time. So, I write code to send an arra...
-
CogInTheWheel10Guy left his computer unlocked. Boss came over looking for him, sat down at his computer and opened lots of ...
So there’s this SOAP api I have to use (not by choice, and not the only one i have to use) that returns a bunch of XML nodes to confirm the data sent made it and checks out - pretty standard stuff yea.
Now every once in a while it doesn’t respond (as far as I could tell) so today I wrapped a debug around the soap call, error handler and responses and threw a bunch of messages it’s way to try and force it not to respond in order to be able to put some decent error handling in place.
Well it wouldn’t fail.
100 messages .... all responses good
100 more.... all responses good
And then 100 more.... all respond with “x”, plain text not XML as expected!
Wtf is this shit!!!!!
rant
dirty dirty soap
going insane
i give up
unexpected
undocumented responses
it’s not me... yay
soap