Permalink
Commits on Jan 18, 2012
  1. re-render server.js

    atmos committed Jan 18, 2012
  2. latest server.js

    atmos committed Jan 18, 2012
  3. fix a redirect follow bug with location headers

    atmos committed Jan 18, 2012
    Redirection without a hostname in the location headers would 404
Commits on Jan 15, 2012
Commits on Jan 14, 2012
  1. Merge pull request #10 from atmos/follow-redirects

    atmos committed Jan 14, 2012
    Follow redirects
  2. version bumps

    atmos committed Jan 14, 2012
  3. start a changelog

    atmos committed Jan 14, 2012
  4. test hella redirect failures

    atmos committed Jan 14, 2012
  5. follow 302s, too

    atmos committed Jan 14, 2012
  6. remove ';' usage

    atmos committed Jan 14, 2012
Commits on Jan 13, 2012
  1. align all the things

    atmos committed Jan 13, 2012
Commits on Jan 10, 2012
  1. Support HTTP 301s

    Dale Hui committed Jan 10, 2012
Commits on Jan 3, 2012
  1. Merge pull request #8 from demersus/master

    atmos committed Jan 3, 2012
    Content Encoding Gzip?
Commits on Jul 1, 2011
Commits on Jun 30, 2011
  1. export the Camo-Host header

    atmos committed Jun 30, 2011
  2. exception whack-a-mole

    atmos committed Jun 30, 2011
  3. Revert "try one of the other error blocks"

    atmos committed Jun 30, 2011
    This reverts commit e2bb1ea.
  4. try one of the other error blocks

    atmos committed Jun 30, 2011
  5. Revert "don't finish off response errors"

    atmos committed Jun 30, 2011
    This reverts commit 93feae8.
  6. don't finish off response errors

    atmos committed Jun 30, 2011
Commits on May 6, 2011
  1. showoff bad regex test

    atmos committed May 6, 2011
Commits on Mar 14, 2011
  1. add a build task

    rtomayko committed Mar 14, 2011
  2. use more aggressive hex encoding instead of url encoding for path format

    rtomayko committed Mar 14, 2011
    Rolling with this for now due to some insane URL decoding in older
    versions of node (<= v0.2.4). Ostensibly, old node versions decode
    the piss out of anything in the path part of the URL, include %2F
    and also squash // characters together. The result is that you cannot
    cleanly separate a URL encoded value in the path.
    
    With this new scheme, every byte of the image URL is encoded into a
    2 char hex value. I actually kind of like it for its similarity to
    the digest hex encoding.
  3. server.js update

    rtomayko committed Mar 14, 2011
  4. URL format docs in the README

    rtomayko committed Mar 14, 2011