HTML edits not showing - html

I’m working on a simple webpage with just an index.html file. If I make changes to the html file and then upload the file to my server, when I reload the page using the url with only http the changes I made show, for example, if I remove the index.html file and reload the page it says could not load page, not found. If I do the same thing but use https, the page still loads even if the index.html file is deleted from the server. I have deleted and cleared cache and website data from my iPhone. This seems to happen on iOS in both safari and Firefox on my iPhone but not on a computer. Does the https cache differently or store files in a different directory?

Related

How can I browse a local html site?

I'm running into two issues trying to browse a local html site on firefox for testing:
When I try to make a link to the root (href="/"), firefox shows the macos root directory on a file browser
When I go to a directory, firefox shows a file browser rather than opening index.html
This seems to be fixed by uploading the site to the internet, but I'd like to be able to test the site locally without uploading it

Github page is not showing and keeps loading

I have published a Github Pages under this link: https://rochanofa.github.io/unesco-seasia/. It is a web-map application based on OpenLayers library.
However, the content of the page is not showing and the page keeps loading forever.
When I open the index.html file in my local directory the content is displayed on my web browser. Here is the screenshot of the webpage when I load from my local computer.
What could I possibly do wrong?
The link to the repository includes the javascript code: https://github.com/rochanofa/unesco-seasia
Looping redirects
I can't tell where it's coming from in the code, but if you load the page with the network tab open, and check "Preserve log" it appears that the root / redirects to unesco-seasia/ and that page redirects back to /. Normally browsers catch this, but it's using HTTP 307, instead of 302 or 301.

Blank page when uploading website files to web hoster

So I downloaded my own portfolio after making it through a portfolio maker and decided to download it, modify the html files to my liking and then wanted to upload them to a web hoster where I would use my own domain for it, however when I tried uploading my files to the main folder on my website's directory and check the website out it simply shows me a blank page, even though it actually displays my logo on the tab on top. When I open the index.html with Chrome from my local files it displays my website perfectly however when I upload it to my website and try view it that's when I get a problem. I have tried using 2 different web hosters and tried uploading my files through FTP and direct upload and still got the same blank page.
NOTE: I uploaded all the files in my site folder not just the index.html and if it works when I opened it with Chrome I don't see why it wouldn't work on my website.
It looks like you have forgotten to upload some files:
All the ones marked 404 are missing and need to be uploaded.

store css file in user system untill client close my website

I am using bootstrap.min.css and my entire website uses this single CSS file for all pages. There are 179 pages on my website and my bootstrap.min.css is just 117Kb
is there any way to store this file on the client's system when he opens home page
and when user moves to the next page how can I use CSS file stored on the client's system ?
this how am linking file this right method
<link href="../../../css/proper align.css" rel="stylesheet">
If the css file is accessed via the exactly same URL (same server, same path, same filename, no attached parameters) and the caching headers are set properly (which they are by default), the file will be cached by the browser.
You can check this behavior using the development tools of your browser.
Here you have a screenshot from the devtools of Google Chrome (hit F12). On the network tab I have selected bootstrap.min.css and I see that it is served from the browsers cache. All fine here. If you don't get it from cache, you can check the caching settings inside the response header.
(http://imgur.com/wSliBMk)
By default the .css file will get cached on client side.
This means it will only be downloaded once for all the 179 pages you have on you website.
All of this caching and reading from cache is handled by the client browser.
If you are not planning on doing any weird "magic" with the css file you won't have to worry about it.
If you reference the same path in the html file the browser will "know" that it has to use the already cached file.
This cache will most of the time persist after the client closes the browser and returns to your website a later time.
Well, the file IS stored on the clients system, it's called caching and is done automatically by browsers. If you reference the same file on all pages, then it's loaded from the same location.
If you worry about bandwidth, I recommend using a CDN-service for your Bootstrap file.
(eg. "//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css")

HTML5 cache downloads root every time

I am playing with HTML5 app cache and right from the beginning I ran into issues:/
I am trying to have simple offline fallback for my page so that there would be nice styled page instead of classic offline error. According to few resources I have red I created this manifest file.
CACHE MANIFEST
# 0.01
CACHE:
NETWORK:
*
FALLBACK:
/ /offline.html
The problem is, that the browser loads into the cache not only the offline.html file, but also the root page, which leads into that page is displayed with lot of errors (no js loaded, no imaged loaded, no CSS, ...) while offline and offline.html is completely bypassed by the browser.
The screenshot below shows logged information about caching progress. You can see there, that the browser downloads both files, instead of only the offline.html as I am trying to do.
All this has been done in latest dev Chrome (23.0.1262.0 dev)
The page which references the manifest file is always included in the offline cache. If you don't want the root page to be cached then you need to create a separate static page to reference the manifest and load it in an iframe.