Rails sending HTTP status code without status message

Question

I have a basic JSON error responder:

format.json { render json: errors, status: :unprocessable_entity }

In development, running Puma, I get back:

Status Code: 422 Unprocessable Entity

In production, running Unicorn, I get back:

Status Code: 422

Can anyone think of a reason that the message would be missing?

I guess it depends on web server and not on Rails

Martin
– Martin

2018-05-03 17:16:12 +00:00
Commented May 3, 2018 at 17:16 — Martin
– Martin, Commented May 3, 2018 at 17:16
Note that HTTP/2 doesn't have reason phrases anymore.

Julian Reschke
– Julian Reschke

2018-05-03 17:24:45 +00:00
Commented May 3, 2018 at 17:24 — Julian Reschke
– Julian Reschke, Commented May 3, 2018 at 17:24

lightyrs · Accepted Answer · 2018-05-03 19:15:25Z

1

Rails sending HTTP status code without status message

is the correct answer in this case.

Once I switched on the 'Protocol' column in Chrome Dev Tools, I was able to see that I was using HTTP/2, which would explain the lack of reason phrases.

Thank you Julian Reschke.

answered May 3, 2018 at 19:15

lightyrs

2,8392 gold badges29 silver badges35 bronze badges

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

Comments

user1977231 · Accepted Answer · 2018-05-03 19:07:43Z

0

It is server and http version related. It will differ from your local and production servers.

answered May 3, 2018 at 19:07

user1977231

Collectives™ on Stack Overflow

Rails sending HTTP status code without status message

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related