Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expected behavior for "Content-Type" header on GET requests for restJson1 #1450

Open
mcmasn-amzn opened this issue Oct 14, 2022 · 0 comments
Open

Expected behavior for "Content-Type" header on GET requests for restJson1 #1450

mcmasn-amzn opened this issue Oct 14, 2022 · 0 comments
Labels
guidance Question that needs advice or information. protocol-test New protocol tests are needed server This issue involves the specification for server software.

Comments

@mcmasn-amzn
Copy link
Contributor

Original issue: smithy-lang/smithy-rs#1845

What is the expected behavior of smithy clients/servers in the restJson1 protocol for the Content-Type header?

The protocol tests have one example showing that a response of HTTP 415 should be given if Content-Type is included on a POST request without a body.

But what about other HTTP verbs like GET, DELETE, or OPTIONS? Should it always be considered a malformed request if Content-Type is included when the request body is empty?
@mcmasn-amzn mcmasn-amzn mentioned this issue Oct 14, 2022
Open
@jvschneid jvschneid added the guidance Question that needs advice or information. label Jul 24, 2023
@kstich kstich added the protocol-test New protocol tests are needed label Aug 15, 2023
@kstich kstich added the server This issue involves the specification for server software. label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
guidance Question that needs advice or information. protocol-test New protocol tests are needed server This issue involves the specification for server software.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jvschneid @kstich @mcmasn-amzn