I’m having an odd problem with WordPress correctly creating an enclosure tag when I link to an mp3 file on my home server. (I want to do this to conserve space/bandwith at my actual ISP).
What’s odd is that when I put the identical file at my ISP and link to it in a post, WP does the right thing and creates the enclosure.
So, obviously I’m thinking that something is not right with my home server, but I’ve tried everything I can think of and it all looks right to me. I’ve verified that I can get actually successfully get the file that sits on my home server via HTTP from my ISP’s machine where WP is running (I assume WordPress at least has to be getting the HTTP headers to get the byte size and content-type information). So that rules out a myriad of problems (dns, firewall, simple boneheaded web server misconfiguration).
I’ve compared the HTTP headers, and don’t see anything interesting:
FROM MY HOME SERVER:
200 OK
Connection: close
Date: Wed, 01 Jun 2005 04:45:59 GMT
Accept-Ranges: bytes
ETag: “ff05-43d4aa-66c0bf00”
Server: Apache/2.0.49 (Fedora)
Content-Length: 4445354
Content-Type: audio/mpeg
Last-Modified: Wed, 01 Jun 2005 03:06:04 GMT
Client-Date: Wed, 01 Jun 2005 04:45:59 GMT
Client-Peer: 216.15.127.159:80
Client-Response-Num: 1
FROM MY ISP:
200 OK
Connection: close
Date: Wed, 01 Jun 2005 04:45:49 GMT
Accept-Ranges: bytes
ETag: “5f00e9-43d4aa-429d261c”
Server: Apache/1.3.33 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.3.10 FrontPage/5.0.2.2635 mod_ssl/2.8.22 OpenSSL/0.9.7a
Content-Length: 4445354
Content-Type: audio/mpeg
Last-Modified: Wed, 01 Jun 2005 03:06:04 GMT
Client-Date: Wed, 01 Jun 2005 04:46:12 GMT
Client-Peer: 216.180.251.58:80
Client-Response-Num: 1
If it helps, the URL to the file at my ISP is
https://realfake.org/software/carter_family-never_grow_old.mp3
and the URL to the file on my home server is
[audio src="https://ezraball.dyndns.org/songoftheday/ezra/carter_family-never_grow_old.mp3" /]