Setting http status codes

Question

redirect_to browse_path(asset.parent_id), notice: "successfully created file!", status: 201

201 is the status you should set if you've created a resource. While the above method works for a create action, the spec for its action no longer does:

subject { response }
describe '.create' do
    context 'when orphan' do
      before do
        post :create, asset: { parent_id: nil, uploaded_file: file }
      end

      it { should have_http_status 201 }
      it { should redirect_to '/' }
    end
end

The status expectation passes, but the redirect_to expectation fails:

Expected response to be a <redirect>, but was <201>

I accept that it's no longer a 302 redirect, but it does still redirect the user to a new route (which I want to test). The redirect_to spec passes if I set it to the "wrong" code of 302, rather than 201:

redirect_to browse_path(asset.parent_id), notice: "successfully created file!", status: 302

so should I bother with setting status codes? I'll admit I actually have no idea how the browser uses them and my applications functions just as well if I painstakingly set them in my actions or don't (just use 302 redirects and 200 successes).

If status codes are important, how should I get my above specs to pass?

I get wrong number of arguments (2 for 1) ?

Starkers
– Starkers

2014-06-29 20:16:11 +00:00
Commented Jun 29, 2014 at 20:16 — Starkers
– Starkers, Commented Jun 29, 2014 at 20:16

zetetic · Accepted Answer · 2014-06-30 00:17:46Z

1

From the docs:

The status code can either be a standard HTTP Status code as an integer, or a symbol representing the downcased, underscored and symbolized description. Note that the status code must be a 3xx HTTP code, or redirection will not occur.

(emphasis added)

Simply put, it is an error to redirect with a 201 status code.

answered Jun 30, 2014 at 0:17

zetetic

47.6k10 gold badges114 silver badges119 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

BookOfGreg · Accepted Answer · 2014-06-30 07:52:03Z

0

You can assert off response.body or other response attributes within rspec. In this case the thing you are after is response.header["Location"]

You can choose to dodge the problem with capybara/rspec where you can assert current_url and still assert the status code.

redirect_to is just a dumb mid level helper and you need to reach to a slightly lower level in response.something or higher level with capybara to get where you want to be.

edited Jun 30, 2014 at 7:52

answered Jun 29, 2014 at 18:48

BookOfGreg

3,7342 gold badges46 silver badges58 bronze badges

2 Comments

Starkers Over a year ago

While I can do this, its(:status){ should eq 201 }, I cannot do its(:path){ should eq '/' }. Path isn't a method of the response object. I've tried inspecting it but can't find what I want... any ideas?

BookOfGreg Over a year ago

response.header["Location"] is where the redirect goes.

Starkers · Accepted Answer · 2014-06-29 19:17:57Z

0

One way is this:

its(:status){ should eq 201 }
its(:location){ should eq 'http://test.host/' }

answered Jun 29, 2014 at 19:17

Starkers

10.6k22 gold badges103 silver badges167 bronze badges

Collectives™ on Stack Overflow

Setting http status codes

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related