4 ms·

The requested URL was not found on this web server: /~aho/Talks/12-09-07_DMR.pdf

deleted 7y ago
[deleted]
dspillett 7y ago
Working fine here. Do you have any DNS level blocking going on for which that server could be a false positive? Alternately (but probably less likely) they may be moving things around and a DNS change hasn't propagated to your upstream resolvers yet. What address does the server name resolve to at your location? Could also mean they have multiple addresses for that name and not all of them point to a host with that file. I'm not in a position to try check that ATM.
- zamadatix 7y ago
  A 404 is a server side error.
  - tonyarkles 7y ago
    All of the things outlined could result in them asking for the document from the wrong server. Works fine here too.
    - zamadatix 7y ago
      DNS blocking doesn't result in a random server being chosen to get a 404 from it results in a connection error. Works fine for me as well, I'm just pointing out the 404 error didn't come from blocking the server.
      - tonyarkles 7y ago
        If it's redirecting to 127.0.0.1 or a local LAN IP or a local proxy or... lots of things that could cause a 404 resulting from confused DNS.
  - dspillett 7y ago
    ... which can result from the wrong server being asked to fulfill a request due to DNS issues. I've seen blocking implemented by responding with another server address that is supposed to give some meaningful responses (an "ad blocked" image instead of the user just getting an unable-to-load image icon, for instance). This is getting less useful as HTTPS becomes more ubiquitous as you need to install your own signing key on the client machines to pull it off and it isn't often with the hassle, but it is still sometimes attempted. I've also seen DNS level blocking send out 127.0.0.1 which strikes me as stupid.
jzebedee 7y ago
I had the same issue, but the Wayback link works: https://web.archive.org/web/20191013203137/http://www.cs.columbia.edu/%7Eaho/Talks/12-09-07_DMR.pdf https://web.archive.org/web/20191013203137/http://www.cs.col...
pg_is_a_butt 7y ago
What browser are you using?

deleted 7y ago

[deleted]

Working fine here. Do you have any DNS level blocking going on for which that server could be a false positive? Alternately (but probably less likely) they may be moving things around and a DNS change hasn't propagated to your upstream resolvers yet. What address does the server name resolve to at your location? Could also mean they have multiple addresses for that name and not all of them point to a host with that file. I'm not in a position to try check that ATM.

zamadatix 7y ago
A 404 is a server side error.
- tonyarkles 7y ago
  All of the things outlined could result in them asking for the document from the wrong server. Works fine here too.
  - zamadatix 7y ago
    DNS blocking doesn't result in a random server being chosen to get a 404 from it results in a connection error. Works fine for me as well, I'm just pointing out the 404 error didn't come from blocking the server.
    - tonyarkles 7y ago
      If it's redirecting to 127.0.0.1 or a local LAN IP or a local proxy or... lots of things that could cause a 404 resulting from confused DNS.
- dspillett 7y ago
  ... which can result from the wrong server being asked to fulfill a request due to DNS issues. I've seen blocking implemented by responding with another server address that is supposed to give some meaningful responses (an "ad blocked" image instead of the user just getting an unable-to-load image icon, for instance). This is getting less useful as HTTPS becomes more ubiquitous as you need to install your own signing key on the client machines to pull it off and it isn't often with the hassle, but it is still sometimes attempted. I've also seen DNS level blocking send out 127.0.0.1 which strikes me as stupid.

jzebedee 7y ago

I had the same issue, but the Wayback link works: https://web.archive.org/web/20191013203137/http://www.cs.columbia.edu/%7Eaho/Talks/12-09-07_DMR.pdf https://web.archive.org/web/20191013203137/http://www.cs.col...

pg_is_a_butt 7y ago

What browser are you using?