likandoe comments

Repositories
Issues
Comments

Results 3 comments of


                                            likandoe

@Consumes incorrectly handles requests with no content type header / potential security risk

> First, the annotations in your sample are not following the proper case. Yes, of course, I'm aware of that. The case was changed by this editor, otherwise the code...

@Consumes incorrectly handles requests with no content type header / potential security risk

> @spericas But wouldn't it be a good idea to clarify in the spec how such a case should be handled? Of course, we have to deal with backwards compatibility....

@Consumes incorrectly handles requests with no content type header / potential security risk

> @chkal I'm always in favor for clarifications, especially the `application/octet-stream` part from the HTTP/1.1 spec. Awesome! thank you so much for your help! I'll now identify the code making...