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.

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

Followup: ReadHandler should return a 'malformed message' on invalid data version filter #15023

Closed
yunhanw-google opened this issue Feb 10, 2022 · 7 comments
Assignees
Labels
deferral candidate Interaction Model Work spec Mismatch between spec and implementation V1.0

Comments

@yunhanw-google
Copy link
Contributor

Followup: This seems pretty broken in that we will return a generic Failure here on the IM level instead of a useful "malformed message" error code.

This problem is not new with this PR, but please make sure there is an issue filed tracking it.

Originally posted by @bzbarsky-apple in #14711 (comment)

@mrjerryjohns
Copy link
Contributor

Is this really a spec issue? I don't see mention in the spec of the specific error that needs to be returned here...

@bzbarsky-apple
Copy link
Contributor

@mrjerryjohns Spec generally says that if action fields are invalid you return InvalidAction, no?

@mrjerryjohns
Copy link
Contributor

@yunhanw-google can you tackle this as well? It's in line with the other PR you already have in this space (#19356).

@yunhanw-google
Copy link
Contributor Author

yes

@andy31415 andy31415 changed the title Followup: This seems pretty broken in that we will return a generic Failure here on the IM level instead of a useful "malformed message" error code. Followup: ReadHandler should return a 'malformed message' on invalid data version filter Jul 18, 2022
@andy31415
Copy link
Contributor

Is this required for v1.0? It looks like unfriendly message, however unsure about the "spec 1.0" tags. Is this a spec failure?

@bzbarsky-apple
Copy link
Contributor

Is this a spec failure?

Technically, yes. The spec defines what error code should be returned here, and we are returning the wrong one.

The "unfriendly message" is just a consequence of how the error code gets logged by the other side, but the wrong error code is the spec issue.

@bzbarsky-apple
Copy link
Contributor

This got fixed in #21374 as far as I can tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deferral candidate Interaction Model Work spec Mismatch between spec and implementation V1.0
Projects
None yet
Development

No branches or pull requests

4 participants