diff options
| author | bors-servo <lbergstrom+bors@mozilla.com> | 2016-01-19 04:24:09 +0530 |
|---|---|---|
| committer | bors-servo <lbergstrom+bors@mozilla.com> | 2016-01-19 04:24:09 +0530 |
| commit | 175b3c2d271cdfdfcac4c3daf5cde3060748b0b8 (patch) | |
| tree | b1111637960ae02aa73157ce71d6f2096ec7a333 /components/script/dom/bindings/codegen | |
| parent | 03a0b73538e58c0fb7e0828ff3371fdd99d0aa0b (diff) | |
| parent | 4165786767f57f475aa8545e3d5ba76a407b3acf (diff) | |
| download | servo-175b3c2d271cdfdfcac4c3daf5cde3060748b0b8.tar.gz servo-175b3c2d271cdfdfcac4c3daf5cde3060748b0b8.zip | |
Auto merge of #9321 - nikkisquared:response_body, r=jdm
Test setting response.body and fetching a message on a server
I've updated http_fetch to now set response.body, as well as written a test to ensure that fetch can retrieve a message on a server. I've also looked into partially implementing some more of http_fetch while trying to figure out where response.body gets written to.
As always I'd like feedback on my logic, I'm confident there are more steps for handling response.body I need but I find the specification difficult to parse on this.
<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9321)
<!-- Reviewable:end -->
Diffstat (limited to 'components/script/dom/bindings/codegen')
0 files changed, 0 insertions, 0 deletions