prjg

If serving XHTML as HTML really offends some people’s sensibilities (apparently it does), then one way around it is the way I do it for part of my site:

In a .htaccess in the doc_root of your blog

RewriteEngine on
RewriteCond %{HTTP_ACCEPT} application/xhtml\+xml
RewriteCond %{HTTP_ACCEPT} !application/xhtml\+xml\s*;\s*q=0
RewriteCond %{REQUEST_URI} \.php$
RewriteCond %{THE_REQUEST} HTTP/1\.1
RewriteRule .* – “[T=application/xhtml+xml; charset=utf-8]”

This serves it is application/xhtml+xml to any user agent that supports that MIME type (nearly everything made in the last 6 or 7 years but IE) and leaves it as the page default, text/html, to those that don’t.

As I said, it’s a major calamity to some people out there to see XHTML served as text/html and the “solution” I’ve provided should help out.

Well, now that I read
https://www.mnot.net/cache_docs/
I may be asking too much for my blog to be cached. It looks like it is by design, because a) it’s a dynamically generated site and b) it sets cookies which cancel out staleness info.

It turns out apache is setting an E-Tag for my pictures and stuff, just not the textual content…

https://www.ircache.net/cgi-bin/cacheability.py
Run your blog’s URL through that and you’ll see what I mean.

So, I’ve probably made a storm in a teacup here – much ado about nothing. ??

You know why they don’t follow W3C standards 100%? Some of those “standards” aren’t worth following or they are vague to begin with – and following them to begin with is optional; it’s not law or mandate despite the W3C’s bizarre use of the word “illegal” to describe non-standard things.

That said, one stands the best chance of having their stuff viewable as intended if one does stick close to “standards”, though nothing is guaranteed obviously.

If you use Firefox as a browser, get thee hence to
https://www.softpedia.com/get/Internet/Other-Internet-Related/CSSViewer.shtml
and download the CSS Viewer extension. Activate it and merely mouse over your page. The extension will highlight whatever CSS is in effect when you mouse over it.

It’s great for things like WP themes which have a bunch of whacky selectors and stuff. You’ll see what I mean.

The ace bit is a quote from the game Wing Commander IV and the Headers part sure is an extension.

https://livehttpheaders.mozdev.org/

Depends on where you see those headers coming out. You didn’t mention.

Everywhere in my /blog/ hierarchy.
See this screenshot Note the expiry date that’s 22 years ago…

No other part of my site does this or issue those headers, just the blog. The other parts of my site are either SSI or perl and neither do this.

I know enough about the way apache works to know it wouldn’t be issuing cache-control and pragma headers unless it was instructed to so. Neither my perl nor SSI parts of my site do this, so why does WP?

What you’re asking me to do is issue a header() instruction to stop apache from issuing no cache headers it *shoudn’t* be issuing in the first place. A bandaid to fix a broken bandaid…

That’s a negatory, ace. No such thing in my wp-config.php file.

Bump, anyone?

It’s silly that people (including me) need to download nearly everything any time they visit simply because of the nutcase way caching is (not) addressed.

To make a long story short, I had to mouse over a bunch of stuff to see what it did/where it lead. Hence my comparison. Sorry you read so far into that.

It’s neither here nor there remember. You asked for opinions, which, by definition, can neither be right nor wrong.

And, I’m a he. Very much so. Well, my kids call me Dad anyway…

That looks wrong. (No joke, huh?). It looks like the first bit has been re-written by mod_rewrite but the rewrite rule is not picking up the latter bit, the ?cat=5 bit, hence the 404.

Maybe post your rewrite rule here and a genius can sort it out for you.

Nah, I’ll leave it. You are illustrating one of the reasons why script-driven CMS’s and blogs drive me nuts. Just to remove something simple you need to edit ~45 different files.

It’s *never* as configurable/editable as boffins make it out.

All the iddy-biddy images to the upper left need to go. Why? Have a read of Vincent Flanders site. He explains it better than I can.

Apart from them, I like it.

It still leaves the preview named anchor at the top of the page (which now goes nowhere) but it works great.

Redirect permanent /old-file https://new-location

See https://httpd.apache.org/docs/2.2/mod/mod_alias.html#redirect

Silly question, but where would one put that? sidebar.php?