Tag Info

New answers tagged

1

Usually all it takes is a single link from one site to another. Once your site is discoverable via links, it will eventually be crawled as the spiders move throughout the web. As for why you are just now seeing it, no idea. There could be a number of factors in play with this, including a simple frequency increase as the search engines decide that you ...


2

Because, in your example, web server would always send CSS and images regardless if the client already has them, thus greatly wasting bandwidth (and thus making the connection slower, instead of faster by reducing latency, which was presumably your intention). Note that CSS, javascript and image files are usually sent with very long expire times for exactly ...


8

Your web browser doesn't know about the additional resources until it downloads the web page (HTML) from the server, which contains the links to those resources. You might be wondering, why doesn't the server just parse its own HTML and send all the additional resources to the web browser during the initial request for the web page? It's because the ...


3

Because it doesn't assume that these things are actually required. The protocol doesn't define any special handling for any particular type of file or user-agent. It does not know the difference between, say, an HTML file and a PNG image. In order to do what you're asking, the Web server would have to identify the file type, parse it out to figure out what ...


6

HTTP2 is based on SPDY and does exactly what you suggest: At a high level, HTTP/2: is binary, instead of textual is fully multiplexed, instead of ordered and blocking can therefore use one connection for parallelism uses header compression to reduce overhead allows servers to “push” responses proactively into client caches More is ...


46

The short answer is "Because HTTP wasn't designed for it". Tim Berners-Lee did not design an efficient and extensible network protocol. His one design goal was simplicity. (The professor of my networking class in college said that he should have left the job to the professionals.) The problem that you outline is just one of the many problems with the ...


10

Because they do not know what those resources are. The assets a web page requires are coded into the HTML. Only after a parser determines what those assets are can the y be requested by the user-agent. Additionally, once those assets are known, they need to be served individually so the proper headers (i.e. content-type) can be served so the user-agent ...


1

Specifying /sbin/nologin as the login shell for the Apache user does not prevent Apache from launching bash. It only prevents logins with the user that is meant to only run the webserver. You might be interested in How do I secure Apache against the Bash Shellshock vulnerability? from the security StackExchange site. It suggests some workarounds like ...



Top 50 recent answers are included