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

Base content type detection on content-type header of request instead of file ending #42

Closed
holycrab13 opened this issue Aug 5, 2024 · 3 comments

Comments

@holycrab13
Copy link
Contributor

The file ending is mandatory at the moment as it is used for content type detection and does not allow saving at arbitrary locations.

Would it be possible to use the content type header instead?

@manonthegithub
Copy link
Collaborator

No. If it were possible, I would have done that.

@holycrab13
Copy link
Contributor Author

Ok, a document format must be detectable always, not only at the time of the request - thus file endings mandatory.

@manonthegithub
Copy link
Collaborator

#38 (comment)

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

2 participants