Skip to content
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

Invalid ‘warning: empty body asset’ for certain status codes #13

Closed
Baggz opened this issue Jul 4, 2013 · 1 comment
Closed

Invalid ‘warning: empty body asset’ for certain status codes #13

Baggz opened this issue Jul 4, 2013 · 1 comment
Assignees

Comments

@Baggz
Copy link

Baggz commented Jul 4, 2013

Hi,

Snow Crash throws a warning ‘empty body asset’ for a response with 304 status code. There should not be a warning according the spec.

If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.

Blueprint

### Get a message [GET]

+ Request

...

+ Response 304

Output

warning: empty body asset
@ghost ghost assigned zdne Jul 4, 2013
@zdne
Copy link
Contributor

zdne commented Jul 11, 2013

This is a bug and will be fixed.

Status codes that MUST NOT include a message-body are:

  • 204
  • 304

@zdne zdne closed this as completed in a9bf977 Jul 15, 2013
pksunkara pushed a commit that referenced this issue Aug 28, 2017
Increase the limit for max nesting to 32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants