[PmbPhy (OP)]

I need some help understanding what's going on. I'm working on a webpage, i.e.

http://www.newenglandphysics.org/physics_world/qm/x_square.htm

It didn't appear to be showing the right version so I deleted that page from the host directory and refreshed the page. I should have gotten an error message since there's no page there to show. However all I got was the same version of the page I just deleted. I can't figure out what to do to correct this problem and why its happening. Can someone help me understand what's happening? Thanks.

[RD]

I need some help understanding what's going on. I'm working on a webpage, i.e.
http://www.newenglandphysics.org/physics_world/qm/x_square.htm

I'm seeing something Frankensteinian :  a 404 message "page not found", but a page is shown : screenshot attached.

[ Sometimes changes take time to percolate through ].

[PmbPhy (OP)]

I need some help understanding what's going on. I'm working on a webpage, i.e.
http://www.newenglandphysics.org/physics_world/qm/x_square.htm

I'm seeing something Frankensteinian :  a 404 message "page not found", but a page is shown : screenshot attached.

[ Sometimes changes take time to percolate through ].

I think that the problem is on my system and not all over the web. I tried deleting the cache and set it so that I'd see a refresh every time I visited the web page. However I keep seeing that same darn page. It's driving me nuts. The main problem being that I can't see how the new pages work and look.

[nicephotog]

First, that's about correct it takes some time to be updated into the nameserver web lookup cache "potentially".
However,
Browser software often requires at least two refresh calls to load the page but more-over, the web page should be made according one of the W3C specified DTD's for any of HTML4 or HTML5
However, again !
other facets inside a page DTD for "http display markup" require an "expires" header to be placed in the HEAD tag of the document to control request reserving to the client browser software.
If the time is "now".
Cache-control and no-cache is about the fact that page information is also store-able on the origin response server (i.e. server side cookies) and not in your browser, this mechanism sometimes needs synchronised values with the page served to understand when to expire or refresh information to the client browser.

HTTP1.1 version
https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
14.9.3 Modifications of the Basic Expiration Mechanism
14.21 Expires