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

File upload #7

Open
dsebastien opened this issue Dec 9, 2016 · 0 comments
Open

File upload #7

dsebastien opened this issue Dec 9, 2016 · 0 comments

Comments

@dsebastien
Copy link
Contributor

Points yet to clarify:

  • whether the charset matters and the impact it can have on requests going through infrastructure components / request interceptors
  • whether the Content-Type matters (same reaons)

We currently recommend using the application/octet-stream as Content-Type and not necessarily specifying the charset (i.e., letting it default to us-ascii. Our reasoning is that in many cases, there should not be any interpretation of the content and it should be saved as is.

Although we need to check this regarding security.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant