tatham

6 ms·

1. 1.▲
   by tatham 14y ago

   Disclaimer: I'm a Principal Consultant with Readify. I'm not familiar with this particular project, however I'd like to clarify a bit based on our engagement focus. Organisations like SEEK engage us to help improve development team process,
2. 2.▲
   by tatham 16y ago

   Suggestions?
3. 3.▲
   by tatham 16y ago

   Heroku was a lot simpler than us spinning up (or paying for) a VPS. The other technologies were mostly just for fun.
4. 4.▲
   by tatham 16y ago

   Nice catch. Seems we need to improve our regex. In our view, only three digit codes are valid.
5. 5.▲
   by tatham 16y ago

   The 300 series is not well supported. Most people don't even know that 307 exists - they always use 302.
6. 6.▲
   by tatham 16y ago

   You're still getting a 418 response there, just not the right status description. Varnish is certainly stuffing us up a bit. There's a note about this at the bottom of the page. If I did this again, I wouldn't deploy it to Heroku for this r
7. 7.▲
   by tatham 16y ago

   Nice! :) Mostly, we wanted to play with some tech and we came across the domain name httpstat.us which we just thought was cool.
8. 8.▲
   by tatham 16y ago

   This will get you 80% of the way there, but some status codes require certain response headers too. We return these too.
9. 9.▲
   by tatham 16y ago

   You're correct - it was all one big experiment so we threw way more technologies at it than we had to. http://isitbeerti.me was another experiment of ours on the .NET platform