If you're using my
TinyURL utility that I originally described
here, you'll need to grab the
latest bits in order for the utility to continue working. It stopped working sometime this month (thanks to Medardas for bringing it to my attention). I had guessed it was due to some small change in the HTML response from
tinyurl.com that was confounding my regular expression search for the result. But it turned out to be due to an HTTP 417 error ("Expectation failed") that was being returned by the server in response to the POST my utility makes.
In particular, the POST request my app was making included an Expect=100-continue header that needed to be removed. Unfortunately, I don't have any packet traces of my original development effort that would confirm who's side of the HTTP conversation changed. Did a recent Windows update cause a change in behavior of the .NET Framework's implementation of HttpWebRequest (and/or supporting code)? Or did tinyurl.com's server-side software undergo an update? I have no idea (not that it matters, other than satisfying my curiosity).
At any rate, once I diagnosed the issue with some help from
Ethereal, the fix was an easy one. I just needed to turn off the 100-continue expectation on my side of the conversation before sending my request:
With that fix in place, everything is back in working order. So be sure to grab the updated bits before your next CTRL-SHIFT-T.
Posted
Feb 22 2006, 11:10 AM
by
mike-woodring