HaCkeD by SA3D HaCk3D
KurDish HaCk3rS WaS Here
FUCK ISIS !
KurDish HaCk3rS WaS Here
FUCK ISIS !
The first thing that should be in your HTML files is a
DOCTYPE declaration. In the past, I have simply copied them when I have used them at all, without really thinking about what was in them. Today, I have decided to take a closer look. At first glance at the W3C Recommended list of Doctype declarations page, it would seem that simply copying a standard
DOCTYPE is the thing to do if you are writing an HTML page. The page states that exact spelling and case are important.
There is a wide range of possible standard
DOCTYPE declarations available. For HTML 4.01, there are three: Strict, Traditional, and Frameset.
If you leave out your
DOCTYPE declaration, the default is HTML 4.01 Strict Document Type, according to W3C. This one disallows deprecated elements and attributes. It “…excludes the presentation attributes and elements the World Wide Web Consortium (W3C) expects to phase out as support for style sheets matures.” It might be a good idea to use Strict elements and attributes if you would like to eventually transition to HTML 5, which is as yet not a standard. You can determine which elements are deprecated by checking the Index of Elements page. Likewise, deprecated attributes can be identified on the Index of Attributes page. Look in the Depr. Column for a D. The Strict
DOCTYPE declaration is as follows:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
If you need to accommodate deprecated elements and attributes, you can use the HTML 4.01 Transitional Document Type. This one allows you to use deprecated elements and attributes but does not allow frames. The Transitional
DOCTYPE declaration is as follows:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
If you are determined to use frames, then you can use the Frameset declaration as follows:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
I noticed that frames and deprecated elements and attributes worked on my test pages even when I declared the pages as Strict. If you really want to know if your pages conform to your chosen type, you can validate your HTML files using the W3C Markup Validation Service. One note about using this service: In addition to requiring the
DOCTYPE declaration, it will also flag an error if you fail to declare your character set. You can do that by including the following in your HTML file:
<HEAD> <META http-equiv="content-type" content="text/html;charset=utf-8"> </HEAD>
Now let’s tease out what the various parts of the
DOCTYPE declaration really mean. The general syntax for
<!DOCTYPE root-element PUBLIC "FPI" ["URI"] [ <!-- internal subset declarations --> ]>
<!DOCTYPE root-element SYSTEM "URI" [ <!-- internal subset declarations --> ]>
If you use HTML as the root-element and don’t declare anything else, you will invoke the HTML 5 version of the DTD, which is as yet non-standard. Some other standard root-elements include
DOCTYPE declarations are used in XML files, you can declare a custom root-element. Like
<HTML>, this custom root-element will surround the contents of the page. For instance, you may have the following:
<?xml version="1.0" standalone="no" ?> <!DOCTYPE memo SYSTEM "memo.dtd"> <memo> </memo>
SYSTEM declares where the definition of the document type resides. If it is
PUBLIC, then it is a publicly accessible object. This is the default. Those standard HTML
DOCTYPE declarations are all
PUBLIC. Their definitions reside where anyone can get to them. If
SYSTEM is declared, then the document type is a system resource, such as a local file or URL.
The FPI used with a
PUBLIC declaration is a string which identifies the owner and the particular document identified by the FPI. In the case of
"-//W3C//DTD HTML 4.01//EN", the owner is
"-//W3C", and the document is
"DTD HTML 4.01//EN". FPI is not used with
The URI identifies where a Document Type Definition (DTD) file defining the document type is located. Describing the contents of this file is beyond the scope of this post. Information about DTD can be found in the Wikipedia post, Document Type Definition.
DOCTYPE declarations also allow DTD statements to be placed directly into the declaration. The following are examples of this:
<?xml version="1.0" standalone="yes" ?> <!DOCTYPE foo [ <!ELEMENT foo (#PCDATA)> ]> <foo>Hello World.</foo>
<?xml version="1.0" standalone="no" ?> <!DOCTYPE document SYSTEM "subjects.dtd" [ <!ATTLIST assessment assessment_type (exam | assignment | prac)> <!ELEMENT results (#PCDATA)> ]>
Let’s say that you want to display the time on your HTML page. You could do it like this in
<html> <body> <!--#config timefmt="%I:%M %p %Z" --> <p><!--#echo var="DATE_LOCAL"--></p> </body> </html>
That works fine as long as your ISP is in the same time zone as you are. But what if it isn’t? You could try changing the time zone in
.htaccess like so:
SetEnv TZ America/Los_Angeles
Unfortunately, this does not work with SSI directives, at least not on my host. The above
test.html file will display 08:02 PM CDT because my host is in Texas. The above
SetEnv does, however, work with PHP. Fortunately, if you’re set on using HTML files, there’s a way to use SSI to call a PHP file. The new
test.html looks like this:
<html> <body> <p><!--#include file="display-local-time.php" --></p> </body> </html>
display-local-time.php looks like this:
<?php echo date("g:i A T e"); ?>
test.html will display 6:02 PM PDT America/Los_Angeles.
You can find a list of supported time zones to set in your
.htaccess file here: http://www.php.net/manual/en/timezones.php
The parameters for the PHP
date function are listed on the reference page here: http://us.php.net/manual/en/function.date.php
Let’s say that you’re building a large Συρματοπλ?γματα website in HTML. The client wants to display a copyright declaration on each page of the site using the current year. If the year is hard-coded on the site on each page, Server this would require yearly updates On of each page on the site. An easier option would wholesale nfl jerseys be to take advantage of Server Side Includes (SSI) Linux features. This, of course, assumes that you have set up SSI on your server as described in my previous posts.
The solution looks like this:
<html> <body> <p>This page demonstrates how to display a copyright notice using the current year an on the server.</p> <!--#config wholesale mlb jerseys timefmt="%Y" --> <p>Copyright © <!--#echo var="DATE_LOCAL"--></p> </body> </html>
This solution takes advantage of two SSI directives,
echo, plus the system variable,
echo directive allows you to display an HTTP environment variable. Availability of a particular environment variable cheap mlb jerseys may depend on the server you are using.
DATE_LOCAL is available on both the Windows IIS server on my local machine and the Apache server on my ISP. The default format cheap jerseys displayed by
<!--#echo var="DATE_LOCAL"--> will depend on how the system is set up. On my Eryaman Windows IIS server, the default looks like Wednesday April 18 2012. On my ISP running Apache, it looks like Wednesday, 18-Apr-2012 11:20:38 CDT. This, however, is not the format desired for the above scenario.
We can configure what format to use for the date by using the
config SSI directive. The following timestamp format codes are available. In our example, we want just the year, so we’ll use
%Y like this:
<!--#config timefmt="%Y" -->.
||Abbreviated Really weekday name||Sun|
||Full weekday name||Sunday|
||Abbreviated month name||Feb|
||Full month name||February|
||Standard date & time||Mon Oct 22 11:21:55 2004|
||Day of month as digit||12|
||Hour number (24-hour clock)||22|
||Hour number (12-hour clock)||10|
||Day of the year as digit||047|
||Month as digit||06|
||AM or PM||PM|
||Day of the week number (with Sunday as first day)||1|
||Date in standard format||01/12/05|
||Time in standard format||12:04:45|
||Two-digit year number||04|
Turning on Server Side Includes on wholesale nba jerseys my ISP’s Apache server turned Worn out to be HTML quite easy. All I needed to wholesale mlb jerseys do was add the following lines to the
.htaccess file in the directory Tukang where the Circle pages reside:
Options +Includes AddOutputFilter INCLUDES .html
Now I can run my test HTML page with the include on my web SSI host.
If you are testing your HTML files with SSI calls Wholesale Miami Dolphins Jerseys on a Windows server, you will need Ankles to set options to allow SSI to be interpreted on the server side. The following are the steps u I took to set up SSI in IIS on my cheap jerseys computer running Windows wholesale jerseys 7 Home Premium.
From the Start menu, click on cheap NFL jerseys Control Panel. Click on Programs. Under Programs and Features, click on Turn Windows features on or off.
In Windows Features, expand Internet Information Services. Expand World Wide Web Services. Expand Application with Development Features. Check the Server-Side Includes box. Then click OK at the bottom of the window.
Then you need to go into the IIS manager. Go to the in Control Panel. Click on System and Security. Click on Administrative Tools. Double-click on Internet Information Services (IIS) Manager to run it.
In the IIS Manager, double-click on Handler Mappings.
Request path: *.html
Click OK at the bottom of the window.
Now your HTML with the SSI include directive should work.
Let’s cheap jerseys say cheap mlb jerseys that cheap jerseys you Sports are Its building Getting a Its site with several different HTML pages. You want them all to have the same template and menu structure. This would require a lot of duplicated code in each page of the site. Wouldn’t it be a lot nicer to have that duplicate code in files that can be included in your pages? There actually is a way to do this, but it may require that you change options for Server Side Includes (SSI) on your server. Those changes to the server will be covered in future posts. For now, let’s look at how to do the include.
The following line will include the file
test2.html into an HTML file.
<!--#include file="test2.html" -->
To test the concept of including one HTML file inside another, I wrote the following page,
<html> <body> <p>Before the include.</p> <!--#include file="test2.html" --> <p>After the include.</p> </body> </html>
test2.html contains the following:
If your server is set up to accept SSI directives, you should see the following:
|Before the include.
After the include.
If you view the source from your browser, it will look like this:
<html> <body> <p>Before the include.</p> <h1>Hello, World!</h1> <p>After the include.</p> </body> </html>
The code from the included file will have been integrated on the server side into the code sent to the client.
If the server has not been correctly configured, you will not see “Hello, World!” in the browser. So what do you do if this is the case? I will cover that in the next two posts: Turning on SSI in IIS on a Windows Server and Turning on SSI in Apache on a Linux Server.
If wholesale nfl jerseys you cheap jerseys want cheap jerseys to We set CommentsUse up Hes your Windows computer to test PHP pages, you will need to set up IIS first. When I had Windows XP, I had to buy the Professional version of the operating system to get IIS. IIS is included in Windows 7 Home Premium. You can find instructions for setting up IIS here: Setting Up IIS 7.0 by Microsoft TechNet. When you get done, you should have an
inetpub directory in your hard drive’s root directory, and there should be a
wwwroot directory within that (
wwwroot directory is where you will put your HTML pages, your PHP pages, and anything else you want to test locally on your Web Server.
At this point, you can test to make sure that standard HTML pages are working properly. You will need to know your computer’s name for the URL to your local pages. Go to the computer’s Control Panel. Click on “System and Security”. Click on “System”. Your computer’s name should be listed on that page. If you have an HTML test file named
test.htm in your wwwroot directory, your URL for your browser should be:
<html> <body> <h1>Hello, world!</h1> <p>This is a test of HTML.</p> </body> </html>
You can find the binaries on the PHP For Windows: Binaries and sources Releases page. If you know the version of PHP that your Internet Service Provider (ISP) is using, it might be a good idea to install the version to match theirs. The ISP for a site I set up for a friend recently upgraded their PHP installation, and there were some changes that had to be made to make the site run properly on the new version. I’ll discuss some of the changes I needed to make in a future post. Having matching versions can help prevent problems, at least until your ISP decides to upgrade.
You can find the instructions at the PHP: Installation on Windows systems – Manual page. The two Windows Installer links will tell you how to install the binaries according to the version you have decided to use. The installation process should set up the options in IIS that are needed for PHP to run. If PHP does not run after installation, the Microsoft IIS links on the PHP: Installation on Windows systems – Manual page should help you get going.
Once you have PHP installed, you can test it. You can use a simple file such as
phpinfo.php in your
wwwroot directory containing the following:
<html> <body> <?php phpinfo(); ?> </body> </html>