summaryrefslogtreecommitdiff
path: root/issues/binderlite/error-regarding-static-assets-after-forwarding.gmi
diff options
context:
space:
mode:
authorjgart2021-09-24 02:38:08 -0400
committerjgart2021-09-24 02:39:16 -0400
commitf8fdd9b271bea21e75c607ca5cfc345734959169 (patch)
treee3135a1935a87a19038ab033b77c42dcdb2d0934 /issues/binderlite/error-regarding-static-assets-after-forwarding.gmi
parentd933c8f10db2f2637bbc4b5c9a729873fce4d314 (diff)
downloadgn-gemtext-f8fdd9b271bea21e75c607ca5cfc345734959169.tar.gz
Close nginx static assets error
Diffstat (limited to 'issues/binderlite/error-regarding-static-assets-after-forwarding.gmi')
-rw-r--r--issues/binderlite/error-regarding-static-assets-after-forwarding.gmi27
1 files changed, 24 insertions, 3 deletions
diff --git a/issues/binderlite/error-regarding-static-assets-after-forwarding.gmi b/issues/binderlite/error-regarding-static-assets-after-forwarding.gmi
index 2670d6a..27e7bd1 100644
--- a/issues/binderlite/error-regarding-static-assets-after-forwarding.gmi
+++ b/issues/binderlite/error-regarding-static-assets-after-forwarding.gmi
@@ -1,8 +1,5 @@
# Nginx forwarding error regarding static assets
-* bug
-* assigned: jgart
-
When nginx forwards the following jupyter notebook url:
`http://localhost/58955/41634c46e4c1ef94b02b646509ae8a7bb023bb4ac7926faa`
@@ -29,3 +26,27 @@ I get the following error (see nginx question in notebooks/user-stories):
[W 04:46:28.181 NotebookApp] 404 GET /static/base/images/favicon.ico (127.0.0.1) 2.610000ms referer=http://localhost/58955/41634c46e4c1ef94b02b646509ae8a7bb023bb4ac7926faa
```
+* closed
+
+See https://git.genenetwork.org/jgart/binderlite/commit/311b85b089e059303041eb2db71d0b1947fe4482
+
+When we paste the token in it allows us to use the notebook successfully
+Then it remembers the cookie and it works in the future.
+
+But if we try a different browser or if we clear cookies in the devtools panel
+(firefox -> storage) then, that cookie will not be saved and we run into the same
+issue.
+
+The nginx config now forwards correctly with the new regex and proper
+proxy_redirect. The new issue is the token having to be manually inputted into
+the form. Subsequent nginx forwards successfully forward the port/url link without
+an issue.
+
+Example token accepted by nginx regex:
+
+```
+http://localhost/49761/?token=f6269bbf48ee5c9887732f5bc76d32f37e1f25483195ae88
+```
+
+The next step is to get jupyter to accept the generated token on the first
+request without needing to input it manually first.