Skip to content

Conversation

wjsi
Copy link
Contributor

@wjsi wjsi commented Apr 15, 2016

When there are non-ascii characters in notebook file name, i.e., "文件名.ipynb", notebooks cannot be properly downloaded via configurable-http-proxy in JupyterHub and an HPE_INVALID_HEADER_TOKEN is reported. After I inspect the headers returned by the notebook, I find that the file name in Content-Disposition header is not escaped, which cause the error in request module of node.js. After escaping the file names, the bug is resolved.

@minrk minrk added this to the 4.2 milestone Apr 15, 2016
@minrk minrk merged commit 32011e3 into jupyter:master Apr 15, 2016
@minrk
Copy link
Member

minrk commented Apr 15, 2016

Thanks!

minrk added a commit that referenced this pull request Apr 15, 2016
When there are non-ascii characters in notebook file name, i.e., "文件名.ipynb", notebooks cannot be properly downloaded via configurable-http-proxy in [JupyterHub](https://github.com/jupyter/jupyterhub) and an HPE_INVALID_HEADER_TOKEN is reported. After I inspect the headers returned by the notebook, I find that the file name in Content-Disposition header is not escaped, which cause the error in [request module](https://github.com/request/request) of node.js. After escaping the file names, the bug is resolved.
yuvipanda pushed a commit to yuvipanda/notebook that referenced this pull request Jul 26, 2016
When there are non-ascii characters in notebook file name, i.e., "文件名.ipynb", notebooks cannot be properly downloaded via configurable-http-proxy in [JupyterHub](https://github.com/jupyter/jupyterhub) and an HPE_INVALID_HEADER_TOKEN is reported. After I inspect the headers returned by the notebook, I find that the file name in Content-Disposition header is not escaped, which cause the error in [request module](https://github.com/request/request) of node.js. After escaping the file names, the bug is resolved.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants