If you invite others to comment on your iWeb blog, and the comment is larger than the 5 MB limit for comments, you may be redirected to a MobileMe warning page. The page is a standard 404 page that asks, "Looking for something special on MobileMe?"
Just created (actually, only modified... it was created by ShoutOut) a new responsive 404 "not found" page with the help of ShoutOut free templates.
https://www.unix.com/status/404.html
Same for 401 and 403 errors.
Picture sans animation:
... (2 Replies)
Made some changes to the forum, so when a page is not found and generates a 404 error, the site redirects to "Today's Posts" page and added a "Not Found" message:
<?php
header('HTTP/1.0 404 Not Found', true, 404);
header("Location: https://www.unix.com/search.php?do=getdaily&redirect=404");... (0 Replies)
I have some industrial ARM linux board with 2.6.34 Linux on it with Busybox
v1.15.0.
The https.conf is located in /etc/ and contains:
H:/root/web
In the www directory I also have 'cgi-bin' folder with chmod 777 and in that folder a file called 'testcgi'.
Now I start the server with... (1 Reply)
I'm trying to send a .zip file from my unix box to my work email (email client outlook)
The file name that I'm trying to sent is sites.zip and this is how I do it:
uuencode sites.zip | mailx -s "testing" myname@mydomain.com
When I open the .zip, the zip is empty. Looking around the we, I... (17 Replies)
I don't want the attachment embedded in the mail. I would like a file attached.
When I do
mailx -s "Report, `date +'%D %r` " -r "Notifications" bob@bob.com < /usr/local/bin/myreport.log> /dev/null
It gets embedded in my email. I want a file attachment. How do I do that? (2 Replies)
PPI::Token::Comment(3pm) User Contributed Perl Documentation PPI::Token::Comment(3pm)NAME
PPI::Token::Comment - A comment in Perl source code
INHERITANCE
PPI::Token::Comment
isa PPI::Token
isa PPI::Element
SYNOPSIS
# This is a PPI::Token::Comment
print "Hello World!"; # So it this
$string =~ s/ foo # This, unfortunately, is not :(
bar
/w;
DESCRIPTION
In PPI, comments are represented by "PPI::Token::Comment" objects.
These come in two flavours, line comment and inline comments.
A "line comment" is a comment that stands on its own line. These comments hold their own newline and whitespace (both leading and trailing)
as part of the one "PPI::Token::Comment" object.
An inline comment is a comment that appears after some code, and continues to the end of the line. This does not include whitespace, and
the terminating newlines is considered a separate PPI::Token::Whitespace token.
This is largely a convenience, simplifying a lot of normal code relating to the common things people do with comments.
Most commonly, it means when you "prune" or "delete" a comment, a line comment disappears taking the entire line with it, and an inline
comment is removed from the inside of the line, allowing the newline to drop back onto the end of the code, as you would expect.
It also means you can move comments around in blocks much more easily.
For now, this is a suitably handy way to do things. However, I do reserve the right to change my mind on this one if it gets dangerously
anachronistic somewhere down the line.
METHODS
Only very limited methods are available, beyond those provided by our parent PPI::Token and PPI::Element classes.
line
The "line" accessor returns true if the "PPI::Token::Comment" is a line comment, or false if it is an inline comment.
SUPPORT
See the support section in the main module.
AUTHOR
Adam Kennedy <adamk@cpan.org>
COPYRIGHT
Copyright 2001 - 2011 Adam Kennedy.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included with this module.
perl v5.10.1 2011-02-26 PPI::Token::Comment(3pm)
