Ah, sorry for confusing you with the other Dave, then. :^)
bfjackMy Common Notification was working fine all through July and August and just this last week and a half has started acting up. We do get occasional notices that e-junkie cannot connect when the site is up and working - at least from the end users point of view. So why e-junkie cannot connect is a mystery - the url hasn't changed.
Hm, if things were working fine before, haven't been touched, and then spontaneously started going awry, that suggests an issue has arisen with the host where your script is running, presumably the same as the seller's own Web site host, possibly just a change in their backbone networking provisions which degraded connectivity along the path across the Internet between their datacenter and ours. Our service automatically sends an email notice to the seller's E-junkie login email whenever your Notification URL fails to respond.
Is there any way to simulate the POSTing process for testing purposes? Is it safe to assume that if a free purchase goes through that a paid one would too?
We'd use exactly the same function to notify your script URL after a Free Checkout as we would after any paid checkout, so that would be a valid test. If you can get it to POST at all even once, that indicates things are fine at our end; moreover, if things weren't fine at our end, we'd be getting reports from everybody since ours is a centrally-managed service where all our functions are shared in common among all users. Any glitches or flakiness in submitting to your script would then be a matter of whether a connection across the Internet to your server can be established, and whether it can respond, on a consistent and reliable basis.
