Oz Michaeli
ae0b630ac7
Fix error when res.set cannot add charset to Content-Type
...
fixes #3303
closes #3305
closes #3307
2017-05-14 23:58:25 -04:00
Douglas Christopher Wilson
82689d68cf
Merge tag '3.19.1'
2015-01-21 03:24:31 -05:00
Douglas Christopher Wilson
855176b633
tests: remove more mocking uses
2015-01-21 03:17:30 -05:00
Douglas Christopher Wilson
db4448dda8
Merge tag '3.9.0'
2014-05-30 22:17:51 -04:00
Douglas Christopher Wilson
3e358458f4
tests: add more etag tests
2014-05-30 19:51:32 -04:00
Jonathan Ong
328c6d3060
remove unnecessary test/support/http
...
backport of 643397ed21
2014-05-18 00:57:54 -04:00
Jonathan Ong
bad55f7977
move setHeader charset patch to .set
...
note that application/json no longer adds charset=utf-8. could be a
regression.
closes #1952
See also: https://github.com/broofa/node-mime/issues/86
2014-03-07 16:32:41 -08:00
Jonathan Ong
643397ed21
remove unnecessary test/support/http
2014-03-05 22:06:14 -08:00
Greg Methvin
4031aaa591
Allow setting an array of header values in the response
...
Make setting multiple header values using an array work as expected.
If the header value is an array, coerce the values to strings instead
of the entire array.
Fixes #1419 .
2013-01-22 18:32:22 -08:00
TJ Holowaychuk
0f5560eebd
updated tests to use "supertest"
2012-06-26 17:14:07 -07:00
TJ Holowaychuk
67ddb429e3
Added: coerce res.set() values to strings
...
if you use res.get() this can bite you in the ass
if you set an etag to a number for example :)
good times
2012-04-26 13:52:37 -07:00
Tj Holowaychuk
3fb7391b97
Added res.set(object) and res.set(field, value) tests
2011-11-08 18:15:31 -08:00
