Dyalog/MiServer

No 404 Page Response?

arcfide opened this issue · 6 comments

When attempting to access a link that doesn't exist in a MiServer site, I get an endless wait with no response from my browser(s). I have tried this on the miserver.dyalog.com page as well as my own sites. Using the Logger extension, I see that the request is logged and that it indicates a 404 response was the correct one, but I don't see any response on the browsers that I have tried. What is going on here?

Can you pls. fetch the latest download from the master-branch - I can't repro with that version...

I have reproduced this on the latest master branch. I note that if I am running Windows, and then launch the MiSite locally, then I can get a 404 page. However, when I launch this same MiSite from a remote virtual machine (Debian Stable), then I get this erratic behavior. The 404 pages don't show up, and sometimes the pages that are accessible don't show up either. It appears that some data is transferred, but something hangs up the transfer at the end.

I can reproduce this at will from http://miserver.dyalog.com. Testing with Edge and Chrome, I tried to access http://miserver.dyalog.com/nothing and I get, well...nothing.

Using Lynx on a local instance I can verify that the 404 HTTP response is in fact sent, but then things just sit around waiting forever for something.

Thanks for that clarification - should facilitate bug-hunting ;-)

Here's what I'm getting from the Windows instance with Logger enabled:

[::ffff:192.168.1.182]:59320 - [21/Aug/2018:16:24:12 +0000] "get /index.mipage" 200 92  3569  1566 
[::ffff:192.168.1.182]:59490 - [21/Aug/2018:16:33:53 +0000] "get /index.mipage" 200 169  3569  1565 
[::ffff:192.168.1.182]:59490 - [21/Aug/2018:16:33:53 +0000] "get /Styles/style.css" 200 5 0 596
[::ffff:192.168.1.182]:59490 - [21/Aug/2018:16:33:54 +0000] "get /upload.mipage" 200 60  1439  705 
[::ffff:192.168.1.182]:59490 - [21/Aug/2018:16:33:54 +0000] "get /Styles/style.css" 200 5 0 596
[::ffff:192.168.1.182]:59490 - [21/Aug/2018:16:33:55 +0000] "get /register.mipage" 404 7  504  504 

And here's what I get from the Linux instance:

[::ffff:68.54.130.14]:59458 - [21/Aug/2018:16:31:55 +0000] "get /index.mipage" 200 53  3577  1561
[::ffff:68.54.130.14]:59458 - [21/Aug/2018:16:31:55 +0000] "get /Styles/style.css" 200 4 0 596
[::ffff:68.54.130.14]:59458 - [21/Aug/2018:16:31:57 +0000] "get /index.mipage" 200 26  3576  1559
[::ffff:68.54.130.14]:59458 - [21/Aug/2018:16:31:57 +0000] "get /Styles/style.css" 200 3 0 596
[::ffff:68.54.130.14]:59472 - [21/Aug/2018:16:33:08 +0000] "get /index.mipage" 200 31  3577  1560
[::ffff:68.54.130.14]:59472 - [21/Aug/2018:16:33:08 +0000] "get /Styles/style.css" 200 3 0 596
[::ffff:68.54.130.14]:59472 - [21/Aug/2018:16:33:09 +0000] "get /favicon.ico" 404 3  0  0
[::ffff:68.54.130.14]:59473 - [21/Aug/2018:16:33:10 +0000] "get /upload.mipage" 200 35  1452  701
[::ffff:68.54.130.14]:59473 - [21/Aug/2018:16:33:10 +0000] "get /Styles/style.css" 200 4 0 596
[::ffff:68.54.130.14]:59473 - [21/Aug/2018:16:33:10 +0000] "get /favicon.ico" 404 2  0  0
[::ffff:68.54.130.14]:59475 - [21/Aug/2018:16:33:13 +0000] "get /register.mipage" 404 3  0  0
[::1]:56548 - [21/Aug/2018:16:56:11 +0000] "get /index.mipage" 200 35  3565  1560
[::1]:56550 - [21/Aug/2018:16:56:25 +0000] "get /index.mipage" 200 47  3565  1559
[::1]:56550 - [21/Aug/2018:16:56:27 +0000] "get /upload.mipage" 200 51  1440  701
[::1]:56550 - [21/Aug/2018:16:56:31 +0000] "get /register.mipage" 404 3  0  0
[::1]:56552 - [21/Aug/2018:16:56:51 +0000] "get /index.mipage" 200 35  3565  1559
[::1]:56552 - [21/Aug/2018:16:56:53 +0000] "get /upload.mipage" 200 48  1440  700

You'll notice that the bytes sent results are a little bit different. You can see the times that I accessed it remotely from my own computer, and the times that I used the local links or lynx browser to access the pages.

Fixed by commit 95fef71