-
Notifications
You must be signed in to change notification settings - Fork 320
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
Serving files from the content API #225
Comments
Pinging @saulshanabrook and @telamonian. They've been thinking about the future of the contents API quite a bit, so I'd like to loop them in here. |
Sounds generally sensible to me on another endpoint. |
How would that differ from existing jupyter_server/jupyter_server/files/handlers.py Lines 14 to 79 in 606487a
I now it is not a part of the contents API, but would it be a good idea to include it in the documentation? |
* add contributing docs * add some local/remote docs
Closing as answered, the documentation issue is tracked in #298 |
As discussed with @Zsailer , the current get content api returns a json object which requires extra parsing in order to be used.
One thing we want to have in ImJoy is an endpoint that can serve the files directly with the correct MIME type in the
Content-Type
header so the browser can render these files directly, like the/view
endpint from the notebook(but it doesn't always give the correct mime type).I think I can build a server extension for it, but definitely nice to have it built-in with the content api.
The text was updated successfully, but these errors were encountered: