
This is driving me absolutely nuts. I have set my E-Journal blog as my home page with Safari. All of a sudden, when I open Safari or click on the home button or even type the URL it downloads a copy of the page instead of displaying it. After that the page usually works fine if I reclick or reenter. Then, after visiting several other sites, it sometimes will again download the E-Journal when I try to go back to it. Sometimes, it doesn't. At the end of a surfing session, it's not unusual to have five or six downloaded copies of the page on my desktop.
It only occurs with that particular site.
This never happened before and inexplicably began on Saturday. Other than standard updates to the E-Journal blog, I haven't added/changed anything - though it certainly is possible that I have somehow coded something wrong.
Others, though, tell me they don't have this problem when they go to the site. It downloads on my main G4 desktop and my 12-inch PowerBook but only in Safari. It doesn't happen with Camino or IE.
I'm wondering if somehow it's the source code on the E-Journal that is causing this.
I have reset, reinstalled and emptied the Safari cache with no success. I have even repaired disk permissions.
I'm at a loss.
UPDATE!
I asked the hosting company based on suggestions so far and they say:
This is not a server-related problem. It is most probably a Safari or a bad-coding issue.Can someone look at the source code and help me figure this out?
Mike-
I can confirm that this downloading problem only started this weekend with your blog using Safari, and it doesn't happen every time (but I have found a bunch of www.mikesejournal.com files on my desktop).
I am wondering if your server provider changed something this weekend, such as the .htaccess file? If you don't think you changed any settings, I'd be looking at the server (a non-professional opinion, by the way, I know only enough to make me dangerous).
T
Posted by: ToeKnee at June 9, 2003 10:38 AMHi,
this problem usually occures, when the http-response which comes from the server misses the information what TYPE the data has. If this information is missing, the browser has to guess and at this point the browser are working differently :-( The correct response type for html should be html/text.
hth
j.f.
Did some more research on the .htaccess files-- it might be a good idea to download the .htaccess files from your mikesjournal and mac-mike blogs and see if they differ.
Also, according to an apache-mime page I found at http://simplythebest.net/info/apache_mime.html the MIME type line for html should read "text/html html htm"
Please check it out yourself, as I am a novice.
T
Posted by: ToeKnee at June 9, 2003 11:12 AMThe problem could be with this tag, although I don't understand why.
[meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /]
This tells the browser the info it's about to get is text/html, usually this comes from the server before the page is even sent, but the meta http-equiv replicates the same behavior. Safari should recognize text/html as something it should _display_ but maybe it doesn't, it is beta afterall.
cgriego-
I don't think that is the problem, because both his Mac-Mike and mikesejournal Moveable Type blogs have the exact same Content-Type meta tags, and this one has not exhibited this behavior.
The point may be moot, though. His mikesejournal now seems to be loading just fine.
T
Posted by: ToeKnee at June 9, 2003 11:42 AM"This is not a server-related problem. It is most probably a Safari or a bad-coding issue."
There is no doubt that this is a "Safari-exclusive" problem, you have already established that by checking other browsers. That being said, a lot of your readers USE Safari, so that is not a helpful answer, especially in light of the fact that many of your readers are Mac users.
My advice would be to find a more Mac-friendly (or overall helpful) web host!
I think this is a server-configuation related problem, myself. I have compared the output of your mikesejournal files when it downloads in the Safari vs. when it displays in Safari, and they are identical. That means to me that it is either a server config problem or a glitch in MT-- but since it just started, I am more inclined to believe something in the Matrix, errr, server has changed.
T
Posted by: ToeKnee at June 9, 2003 12:22 PMI believe it is a coding issue on my part that Safari trips up on...
I added a bunch of links on the bottom right column over the weekend and that's when the glitch started.
I'm looking but unsure what for :-)
Best way to debug these problems is to use lwp-request, part of perl. To get it:
sudo perl -MCPAN -e shell
install Bundle::LWP
Careful: HFS is case-insensitive. There's a handy utility named "head" and LWP is going to install HEAD, which will wallop it. Simplest workaround: make a copy of head, run the install, and move GET and HEAD around as necessary.
That installs a script lwp-request (make sure it's in your path, I moved HEAD and GET to /usr/local/bin).
Sheesh... anyway:
GET -USed / | pbcopy
which dumps the headers and a bunch of other stuff into the clipboard so I can paste it here:
GET /
User-Agent: lwp-request/2.01
GET / --> 200 OK
Connection: close
Date: Tue, 10 Jun 2003 02:59:26 GMT
Accept-Ranges: bytes
ETag: "494019-221ba-3ee53ecd"
Server: Apache/1.3.27 (Unix) mod_log_bytes/1.2 mod_bwlimited/1.0 PHP/4.3.1 FrontPage/5.0.2.2510 mod_ssl/2.8.14 OpenSSL/0.9.6b
Content-Length: 139706
Content-Type: text/html
Content-Type: text/html; charset=iso-8859-1
Last-Modified: Tue, 10 Jun 2003 02:13:33 GMT
Client-Date: Tue, 10 Jun 2003 02:59:29 GMT
Client-Peer: (my ip c3ns0r3d):80
Client-Response-Num: 1
Link: ; /="/"; rel="stylesheet"; type="text/css"
Link: ; /="/"; rel="alternate"; title="RSS"; type="application/rss+xml"
Link: ; /="/"; rel="EditURI"; title="RSD"; type="application/rsd+xml"
Title: Mike Wendland's E-Journal
X-Meta-DC.Title: Mike Wendland's E-Journal
X-Meta-ICBM: 42.32853,-83.05312
MMM.... Gets your server response headers *and* your META tags all in one neat display.
Anyway, looks like you fixed it, but I thought others might find this tip handy. Nice little one-liner... HEAD does a head request, which might be helpful debugging other probos.
Posted by: scooby at June 9, 2003 11:07 PMThat's a terrific resource! Thanks.
Posted by: Mike Wendland at June 10, 2003 08:29 AMThere's an even simpler way to look at HTTP headers using MacOSX, and it doesn't even require installing any extra software (it uses curl, which is a standard part of the OSX BSD subsystem.) Note that this only gets you the HTTP headers, but not the meta tags [and you can get those with a little selective GREPing and use of some other curl options)
curl --head "http://www.mac-mike.com
HTTP/1.1 200 OK
Date: Fri, 13 Jun 2003 15:43:56 GMT
Server: Apache/1.3.27 (Unix) mod_log_bytes/1.2 mod_bwlimited/1.0 PHP/4.3.1 FrontPage/5.0.2.2510 mod_ssl/2.8.14 OpenSSL/0.9.6b
Last-Modified: Fri, 13 Jun 2003 14:57:13 GMT
ETag: "2816d-f9ba-3ee9e649"
Accept-Ranges: bytes
Content-Length: 63930
Content-Type: text/html
Mike:
I can't help you but I can tell you that I use b2 as my blogging software and Safari does not permit the "log in" function to work, I have to use IE for this. Safari is clearly not 100%. I sent this bug report to Apple a couple of months ago. So far nothing.
Bruce
Posted by: Bruce at June 9, 2003 10:33 AM