Notebook gets Malformed HTTP headers from Chrome
- Dominant language
- Jupyter Notebook
- Stars
- 13.3k
- Forks
- 5.8k
- Avg merge
- 6d 11h
- Merged PRs (30d)
- 7
Description
When I attempt to view notebook at localhost:8888 in chrome, the connection times out, and jupyter notebook generates the following message:
`[I 09:08:25.604 NotebookApp] Malformed HTTP message from ::1: Malformed HTTP headers: ''`
I have also received:
`Malformed HTTP message from ::1: Malformed HTTP headers: '\n\x05z\xc2\xaf\xc3\xa3\xc2\xa0\xc3\x90TP\x03\xc3\x9eSe\xc2\xa3\xc2\x96\xc2\x98\xc3\xab+\xc3\x84\xc3\xbd\xc2\x8a\x19\xc2\x861\xc3\xac3G\x00\x00 \n\n'`
Everything works just fine in safari.
My setup is as follows:
macOS sierra 10.12.13
chrome 56.0.2924.87 (64-bit)
jupyter 4.2.0
jupyter notebook 4.2.3
and I'm simply running jupyter notbook from the command line. I get the following log ouput on launch, which I assume is normal:
> [I 08:51:09.307 NotebookApp] [nb_conda_kernels] enabled, 3 kernels found
> [I 08:51:09.729 NotebookApp] ✓ nbpresent HTML export ENABLED
> [W 08:51:09.729 NotebookApp] ✗ nbpresent PDF export DISABLED: No module named nbbrowserpdf.exporters.pdf
> [I 08:51:09.734 NotebookApp] [nb_conda] enabled
> [I 08:51:09.813 NotebookApp] [nb_anacondacloud] enabled
> [I 08:51:09.819 NotebookApp] Serving notebooks from local directory: /Users/ianriley/Development/kaggle
> [I 08:51:09.819 NotebookApp] 0 active kernels
> [I 08:51:09.819 NotebookApp] The Jupyter Notebook is running at: http://localhost:8888/
> [I 08:51:09.819 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
>
I noticed the pdf warning message, but figured it's not important to viewing a notebook in a browser.
Contributor guide
Research direction
Start by reproducing the localhost:8888 connection in Chrome 56 on macOS Sierra with Jupyter Notebook 4.2.3, then compare the server output and behavior with Safari. The issue is resolved when Chrome can load the notebook without timeout or malformed HTTP header messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100