jshttp / etag / 135

Builds Branch Commit Type Ran Committer Via Coverage
135 master Use SHA1 instead of MD5 for ETag hashing closes #17 closes #18 push Douglas Christopher Wilson travis-ci pending completion   set done
134 master bench: run benchmarks with Node.js 6.9.1 push dougwilson travis-ci pending completion   set done
133 master build: support Node.js 7.x push dougwilson travis-ci pending completion   set done
132 master build: Node.js@6.9 push dougwilson travis-ci pending completion   set done
131 master build: Node.js@4.6 push dougwilson travis-ci pending completion   set done
130 master lint: use standard style push dougwilson travis-ci pending completion   set done
129 master lint: use standard style push dougwilson travis-ci pending completion   set done
128 master lint: use standard style push dougwilson travis-ci pending completion   set done
127 master build: istanbul@0.4.5 push dougwilson travis-ci pending completion   set done
126 master build: benchmark@2.1.2 push dougwilson travis-ci pending completion   set done
125 master build: Node.js@5.12 push dougwilson travis-ci pending completion   set done
124 master build: istanbul@0.4.4 push dougwilson travis-ci pending completion   set done
123 master 1.7.1 Pull #18 web-flow travis-ci pending completion   set done
122 master Issue 17 - Use of md5 is not FIPS compliant. Provide ability to customize hash algorithm. Pull #18 web-flow travis-ci pending completion   set done
121 master docs: clarify this is for HTTP ETags closes #16 push dougwilson travis-ci pending completion   set done