Talk:Analog
From DreamHost
| Comments or questions about the article itself are appropriate in article "Talk" pages. The wiki is primarily a documentation tool, and is generally not the place to ask questions that are not specifically related to the article. Please use the Customer Forum, or the Control Panel, to ask questions or to discuss a subject or policy. If you are going to leave comments on a talk page, please sign your comment with four tildes "~~~~", which will insert your user name and timestamp your comments. |
Is there anywhere else I can access this from? My CMS tries to interpret the /stats address as a page within it, and I get a 404 error. --Adamfreeland 20:56, 3 November 2007 (PDT)
- Please don't use the article talk pages to ask for help or general questions (use the DreamHost Discussion Forums) - That said, you will probably find the solution to your problem on the Making stats accessible with htaccess page. I've also edited the article to include a note regarding such circumstances. -- Rlparker 04:49, 4 November 2007 (PST)
Restoring UTF-8 without installing one's own Analog
One can restore the scrambled UTF-8 with
#!/usr/bin/perl
# analog2utf8 -- turn ISO-8859-1 and escape sequence stuff to utf8
#Input: an analog(1) produced index.html
#Output: "fixed" HTML
use strict;
use warnings;
use URI::Escape;
use Text::Iconv;
my $converter = Text::Iconv->new( "big5", "utf-8" );
while (<>) {
s/((?:encoding|charset)="?)ISO-8859-1/$1utf-8/ if 1 .. /<html>/i;
s/\\x([[:xdigit:]]{2})/%$1/g;
$_ = uri_unescape($_);
$_ = $converter->convert($_) if /=big5/; #very few
print;
}
## Didn't try SEARCHCHARCONVERT OFF, however I need to convert many
## more places in the output than the documents mention it does.
Jidanni 00:48, 6 March 2009 (UTC)
Passwords visible in Analog results
Every once in a while, there is a "hiccup" and stats passwords end up in Analog reports. Thus any users one has established stats accounts for can see them.
Dreamhost is waiting for a better version of Analog to fix this. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545322
Here's how one can check to see if they are affected
$ find ~/logs -type f ! -name \*.png |2>&- xargs zgrep '://.\+:.\+@.\+/stats'
Then ask DH to change the permissions of the affected files to allow you to edit out the damage.
Jidanni 22:02, 9 September 2009 (UTC)
