DOCSLIB.ORG

Overall Score for Your Score Is 56% | Grade B

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SeoSiteCheckup Report Overall score for http://www.powerpumpconcrete.com/ Your Score is 56% | Grade B 28 Important Fixes 0 Semi-Important Fixes 31 Passed Checks Title The title of your page have a length of 47 characters. Most search engines will truncate titles to 70 characters. Concrete Leveling & Repair - Powerpump Concrete Description The meta-description tag is missing from your page. You should include this tag in order to provide a brief description of your page which can be used by search engines or directories. HOW TO FIX In order to pass this test you must include a meta-description tag in your page header (<head> section): <head> <meta name="description" content="type_here_your_description"> </head> Note that in HTML the <meta> tag has no end tag but in XHTML this tag must be properly closed. Meta description can have any length but a good practice is to keep this up to 160 characters (search engines generally truncate snippets longer than this value). Keywords The meta-keywords tag is missing from your page. You should include meta-keywords to help indicate what your page is about to search engines. HOW TO FIX In order to pass this test you must include a meta-keywords tag in your page header (<head> section): <head> <meta name="keywords" content="keyword1, keyword2, keyword3"> </head> Separate keywords with commas and don't use any other punctuation beyond commas. Note that in HTML the <meta> tag has no end tag but in XHTML this tag must be properly closed. Most Common Keywords Test It appears that you can further optimize the density of your keywords above. Various sources indicate that a safe keyword density should range between 2-4% for your targeted keywords. concrete - 12 times - 9.16% slab - 4 times - 3.05% offer - 4 times - 3.05% powerpump - 3 times - 2.29% replacement - 3 times - 2.29% HOW TO FIX In order to pass this test, you must optimize the density of your primary keywords displayed above. If the density of a specific keyword is below 2% you must increase it and if the density is over 4% you must decrease it. Keyword Usage Your most common keywords are not appearing in one or more of the meta-tags above. Your primary keywords should appear in your meta-tags to help identify the topic of your webpage to search engines. Keyword(s) included in Meta-Title Tag Keyword(s) not included in Meta-Description Keyword(s) not included in Meta-Keywords Tag HOW TO FIX First of all, you must make sure that your page is using the title, meta-description and meta-keywords tags. Second, you must adjust these tags content in order to include some of the primary keywords displayed above. <h1> Headings Status Your page contains H1 headings. Their contents are listed below: Concrete Leveling & Repair Raise it! Don’t replace it! 574.849.4134 Welcome to Powerpump Concrete CALL FOR A FREE ESTIMATE!   574-849-4134 News / Blog <h2> Headings Status Your page does not contain any H2 headings. H2 headings help describe the sub-topics of your webpage to search engines. While less important than good meta-titles and descriptions, H1 and H2 headings may still help define the topics of your page to search engines. HOW TO FIX In order to pass this test you must indentify the most important sub-topics from your page and insert those sub-topics between <h2>...</h2> tags. Example: <h2>First sub-topic goes here</h2> ... <h2>Another sub-topic</h2> Robots.txt Test Congratulations, your site uses a "robots.txt" file and the URL is: http://www.powerpumpconcrete.com/robots.txt. You may want to use Google's robots.txt analysis tool to check that you are using valid syntax and confirm the directories that you are allowing/blocking for robots. Sitemap Test Congratulations! Your site has a "sitemap" file and the URL is http://www.powerpumpconcrete.com/sitemap.xml. You may want to confirm that you've submitted your sitemap to Google and that it is correctly formatted. Favicon Test and Validator Congratulations! Your website appears to have a favicon. Page Objects Total: 44; Html pages: 1; Images: 5; Css files: 7; Scripts: 7; Css images: 24; Video files: 0; Your page has more than 20 http requests, which can slow down page loading. You can try reducing http requests through various methods such as using text instead of images, using css sprites, using data URIs instead of images, or combining several external files together into one. Html files: 8.18 Kb 8.18 KB http://www.powerpumpconcrete.com/ CSS files: 24.27 Kb 7.17 KB http://www.powerpumpconcrete.com/css/styles.css 0.05 KB http://www.powerpumpconcrete.com/css/index.css 10.63 KB http://www.powerpumpconcrete.com/includes/estro-slider/themes/neutral/skin.min.css 1.22 KB http://www.powerpumpconcrete.com/includes/estro-slider/estro-slider.css 2.38 KB http://www.powerpumpconcrete.com/includes/jqlb/css/jqlb.css + Show More Scripts: 181.76 Kb 15.42 KB http://www.powerpumpconcrete.com/includes/jqlb/jqlb.js 0.66 KB http://www.powerpumpconcrete.com/includes/javascript/general.js 1.40 KB http://www.powerpumpconcrete.com/includes/javascript/scripts.js 91.25 KB http://ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js 35.05 KB [...] ro-slider/jquery.pixelentity.kenburnsSlider.min.js + Show More Images: 246.26 Kb 6.38 KB http://www.powerpumpconcrete.com/i/logo.png 3.29 KB http://www.powerpumpconcrete.com/i/small_logo.png 1.43 KB http://www.powerpumpconcrete.com/i/footer_bg.png 122.60 KB http://www.powerpumpconcrete.com/i/header_bg.jpg 112.56 KB http://www.powerpumpconcrete.com/i/slideshow-1.jpg Css Images: 131.91 Kb 122.60 KB http://www.powerpumpconcrete.com/i/header_bg.jpg 0.32 KB http://www.powerpumpconcrete.com/i/red_bg.png 1.43 KB http://www.powerpumpconcrete.com/i/footer_bg.png 0.36 KB http://www.powerpumpconcrete.com/img/spinner.gif 0.36 KB http://www.powerpumpconcrete.com/img/video.png + Show More Total Page Size: 0.58 Mb Largest Resource: 122.60 KB http://www.powerpumpconcrete.com/i/header_bg.jpg Smallest Resource: 0.05 KB http://www.powerpumpconcrete.com/css/index.css Code To Text Ratio Your page size (source code) is 8.20 Kb and your content text size is 1.50 Kb. Your content text represents 18.29% from your webpage source code. This is a good text to HTML code ratio! URL SEO Friendly Test The URL and all links inside this page are SEO friendly Broken Links Test From 13 distinct anchor links analyzed, 3 of them seems to be broken. Check this list for more details about HTTP status codes. Broken links are listed below: STATUSCODE:302 http://www.powerpumpconcrete.com/blog STATUSCODE:302 http://www.powerpumpconcrete.com/blog STATUSCODE:302 http://www.powerpumpconcrete.com/blog HOW TO FIX In order to pass this test you must identify within your page all the reported broken links and replace the content of the href attribute with a proper URL. Google Analytics Test Congratulations! Your website is using the asynchronous version of Google Analytics tracking code. Underscores in Links Test Congratulations! We have not found underscores in your in-page URLs! Google PageRank Test Google PageRank (PR) is not available for your website. Alexa Page Rank Test Alexa Page Rank is not available for your website. HOW TO FIX Some best practices for increase your Alexa Page Rank are listed below: The most important thing is the content: write useful and qualitative content Regularly submit fresh and unique content Increase the traffic on your site Generate quality backlinks on your website Connect to social networking sites Install Alexa Toolbar on your browser and Alexa Rank Widget into your webpage Verify your website on Alexa.com Image Alt Test Your webpage has 3 images, 3 of them are unique and all of them has an alt attribute. Inline CSS Test Your webpage is using 6 inline CSS properties! HOW TO FIX Is a good practice to move all the inlines CSS rules into an external file in order to make your page "lighter" in weight and decreasing the code to text ratio. check the HTML code of your page and identify all style attribute for each style attribute found you must proper move all declarations in the external CSS file and remove the style attribute For example: <!--this HTML code with inline CSS rule:--> <p style="color:red; font-size: 12px">some text here</p> <!--would became:--> <p>some text here</p> <!--and the rule added into your CSS file:--> p{color:red; font-size: 12px} Media Print Test Your webpage doesn't take the advantages of media print CSS rule! Here are some tips on how to set up a print style sheet. HOW TO FIX For printing your webpage in a user-friendly format you can use one of these methods: 1. Use a @media print {...} rule at the end of your CSS file (note that specificity and precedence rules still apply!) Example: @media print { /* your print styles go here */ #header, #footer, #menu { display: none; } body { font: 12pt georgia,serif; } h1 { font-size: 18pt; } h2 { font-size: 16pt; color: #000; } } 2. Create and use a print stylesheet: <link rel="stylesheet" href="print.css" type="text/css" media="print" /> The file, print.css is the print stylesheet, and the media="print" command means that this CSS file only gets called up when your page is printed. The only CSS rules you need to put in the print stylesheet are ones to override the CSS rules in the main stylesheet (you don't need to repeat any colour or branding CSS commands as they'll already be taken from the main stylesheet).
Recommended publications
  • Open Source Used in Cisco 7600 Wireless Security Gateway Release 4.4

    Open Source Used in Cisco 7600 Wireless Security Gateway Release 4.4

    Open Source Used In Cisco 7600 Wireless Security Gateway Release 4.4 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Open Source Used In Cisco 7600 Wireless Security Gateway Release 4.4 1 Text Part Number: 78EE117C99-66606837 Open Source Used In Cisco 7600 Wireless Security Gateway Release 4.4 2 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-66606837 Contents 1.1 Apache HTTP Server 2.2.3 :5.0.0.0801182 1.1.1 Available under license 1.2 audit 1.2.9 :7.0.0 1.2.1 Available under license 1.3 base-passwd 3.5.7 :11.0.0.0801182 1.3.1 Available under license 1.4 bash 3.0 :6.0.2.0801182 1.4.1 Available under license 1.5 binutils 2.17.50 :10.0.5.0801182 1.5.1 Available under license 1.6 busybox 1.6.0 :7.0.2.0801182 1.6.1 Available under license 1.7 busybox-static 1.6.0 :7.0.2.0801182 1.7.1 Available under license 1.8 cron 3.0pl1 :5.0.2.0801182 1.8.1 Available under license 1.9 db 4.3.28 :1.0.0.0801182 1.9.1 Available under license 1.10 e2fsprogs 1.41.3 :1.0.0 1.10.1 Available
  • The Origins of the Underline As Visual Representation of the Hyperlink on the Web: a Case Study in Skeuomorphism

    The Origins of the Underline As Visual Representation of the Hyperlink on the Web: a Case Study in Skeuomorphism

    The Origins of the Underline as Visual Representation of the Hyperlink on the Web: A Case Study in Skeuomorphism The Harvard community has made this article openly available. Please share how this access benefits you. Your story matters Citation Romano, John J. 2016. The Origins of the Underline as Visual Representation of the Hyperlink on the Web: A Case Study in Skeuomorphism. Master's thesis, Harvard Extension School. Citable link http://nrs.harvard.edu/urn-3:HUL.InstRepos:33797379 Terms of Use This article was downloaded from Harvard University’s DASH repository, and is made available under the terms and conditions applicable to Other Posted Material, as set forth at http:// nrs.harvard.edu/urn-3:HUL.InstRepos:dash.current.terms-of- use#LAA The Origins of the Underline as Visual Representation of the Hyperlink on the Web: A Case Study in Skeuomorphism John J Romano A Thesis in the Field of Visual Arts for the Degree of Master of Liberal Arts in Extension Studies Harvard University November 2016 Abstract This thesis investigates the process by which the underline came to be used as the default signifier of hyperlinks on the World Wide Web. Created in 1990 by Tim Berners- Lee, the web quickly became the most used hypertext system in the world, and most browsers default to indicating hyperlinks with an underline. To answer the question of why the underline was chosen over competing demarcation techniques, the thesis applies the methods of history of technology and sociology of technology. Before the invention of the web, the underline–also known as the vinculum–was used in many contexts in writing systems; collecting entities together to form a whole and ascribing additional meaning to the content.
  • Annotea: an Open RDF Infrastructure for Shared Web Annotations

    Annotea: an Open RDF Infrastructure for Shared Web Annotations

    Proceedings of the WWW 10th International Conference, Hong Kong, May 2001. Annotea: An Open RDF Infrastructure for Shared Web Annotations Jos´eKahan,1 Marja-Riitta Koivunen,2 Eric Prud’Hommeaux2 and Ralph R. Swick2 1 W3C INRIA Rhone-Alpes 2 W3C MIT Laboratory for Computer Science {kahan, marja, eric, swick}@w3.org Abstract. Annotea is a Web-based shared annotation system based on a general-purpose open RDF infrastructure, where annotations are modeled as a class of metadata.Annotations are viewed as statements made by an author about a Web doc- ument. Annotations are external to the documents and can be stored in one or more annotation servers.One of the goals of this project has been to re-use as much existing W3C technol- ogy as possible. We have reacheditmostlybycombining RDF with XPointer, XLink, and HTTP. We have also implemented an instance of our system using the Amaya editor/browser and ageneric RDF database, accessible through an Apache HTTP server. In this implementation, the merging of annotations with documents takes place within the client. The paper presents the overall design of Annotea and describes some of the issues we have faced and how we have solved them. 1Introduction One of the basic milestones in the road to a Semantic Web [22] is the as- sociation of metadata to content. Metadata allows the Web to describe properties about some given content, even if the medium of this content does not directly provide the necessary means to do so. For example, ametadata schema for digital photos [15] allows the Web to describe, among other properties, the camera model used to take a photo, shut- ter speed, date, and location.
  • Javascript Hijacking Brian Chess, Yekaterina Tsipenyuk O'neil, Jacob West

    Javascript Hijacking Brian Chess, Yekaterina Tsipenyuk O'neil, Jacob West

    JavaScript Hijacking Brian Chess, Yekaterina Tsipenyuk O'Neil, Jacob West March 12, 2007 Summary An increasing number of rich Web applications, often called AJAX applications, make use of JavaScript as a data transport mechanism. This paper describes a vulnerability we term JavaScript Hijacking, which allows an unauthorized party to read sensitive data contained in JavaScript messages. The attack works by using a <script> tag to circumvent the Same Origin Policy enforced by Web browsers. Traditional Web applications are not vulnerable because they do not use JavaScript as a data transport mechanism. We analyzed the 12 most popular AJAX frameworks, including 4 server-integrated toolkits – Direct Web Remoting (DWR), Microsoft ASP.NET AJAX (a.k.a. Atlas), XAJAX and Google Web Toolkit (GWT) -- and 8 purely client-side libraries -- Prototype, Script.aculo.us, Dojo, Moo.fx, jQuery, Yahoo! UI, Rico, and MochiKit. We determined that among them only DWR 2.0 implements mechanisms for preventing JavaScript Hijacking. The rest of the frameworks do not explicitly provide any protection and do not mention any security concerns in their documentation. Many programmers are not using any of these frameworks, but based on our findings with the frameworks, we believe that many custom-built applications are also vulnerable. An application may be vulnerable if it: • Uses JavaScript as a data transfer format • Handles sensitive data We advocate a two-pronged mitigation approach that allows applications to decline malicious requests and prevent attackers from directly executing JavaScript the applications generate. 1. Introduction1 Although the term “Web 2.0” does not have a rigorous definition, it is commonly used in at least two ways.
  • Ajax for Dummies (2006).Pdf

    Ajax for Dummies (2006).Pdf

    01_785970 ffirs.qxp 1/20/06 10:51 AM Page iii Ajax FOR DUMmIES‰ by Steve Holzner, PhD 01_785970 ffirs.qxp 1/20/06 10:51 AM Page ii 01_785970 ffirs.qxp 1/20/06 10:51 AM Page i Ajax FOR DUMmIES‰ 01_785970 ffirs.qxp 1/20/06 10:51 AM Page ii 01_785970 ffirs.qxp 1/20/06 10:51 AM Page iii Ajax FOR DUMmIES‰ by Steve Holzner, PhD 01_785970 ffirs.qxp 1/20/06 10:51 AM Page iv Ajax For Dummies® Published by Wiley Publishing, Inc. 111 River Street Hoboken, NJ 07030-5774 www.wiley.com Copyright © 2006 by Wiley Publishing, Inc., Indianapolis, Indiana Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permit- ted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions. Trademarks: Wiley, the Wiley Publishing logo, For Dummies, the Dummies Man logo, A Reference for the Rest of Us!, The Dummies Way, Dummies Daily, The Fun and Easy Way, Dummies.com, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc.
  • Statistics for Donauschwaben-Usa.Org (2009-03)

    Statistics for Donauschwaben-Usa.Org (2009-03)

    Statistics for donauschwaben-usa.org (2009-03) Statistics for: donauschwaben-usa.org Last Update: 03 Apr 2009 - 14:14 Reported period: Month Mar 2009 When: Monthly history Days of month Days of week Hours Who: Organizations Countries Full list Hosts Full list Last visit Unresolved IP Address Robots/Spiders visitors Full list Last visit Navigation: Visits duration File type Viewed Full list Entry Exit Operating Systems Versions Unknown Browsers Versions Unknown Referrers: Origin Referring search engines Referring sites Search Search Keyphrases Search Keywords Others: Miscellaneous HTTP Status codes Pages not found Summary Reported period Month Mar 2009 First visit 01 Mar 2009 - 00:17 Last visit 31 Mar 2009 - 23:17 Unique visitors Number of visits Pages Hits Bandwidth 2112 2781 15381 71620 4.59 GB Viewed traffic * (1.31 visits/visitor) (5.53 Pages/Visit) (25.75 Hits/Visit) (1732.12 KB/Visit) Not viewed traffic * 8539 10927 896.73 MB * Not viewed traffic includes traffic generated by robots, worms, or replies with special HTTP status codes. Monthly history Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2009 2009 2009 2009 2009 2009 2009 2009 2009 2009 2009 2009 Month Unique visitors Number of visits Pages Hits Bandwidth Jan 2009 0 0 0 0 0 Feb 2009 0 0 0 0 0 Mar 2009 2112 2781 15381 71620 4.59 GB Apr 2009 0 0 0 0 0 May 2009 0 0 0 0 0 Jun 2009 0 0 0 0 0 Jul 2009 0 0 0 0 0 Aug 2009 0 0 0 0 0 Sep 2009 0 0 0 0 0 Oct 2009 0 0 0 0 0 Nov 2009 0 0 0 0 0 Dec 2009 0 0 0 0 0 Total 2112 2781 15381 71620 4.59 GB Days of month 01 02 03 04 05 06 07 08
  • Copyrighted Material

    Copyrighted Material

    15_043067 bindex.qxd 6/15/06 7:38 PM Page 330 INDEX accessing XML on server, 172–173 A downloading and installing, 170–171, 176 absolute positioning, 288–289 downloading XML data, 174–175 add function, 40–41 stripping out whitespace, 172, 173, 174 addition function for XML data extraction, 82–83 URL encoding, 171 addition operator (+) (JavaScript), 40, 44, 45 alert boxes Ajax (Asynchronous JavaScript + XML). See also Ajax display by JavaScript function, 30–31 XMLHttpRequest frameworks; object displaying, 28–29 advantages, 2, 3, 62 displaying text from text fields, 37 attributes, 29, 262–263 aligning text in CSS, 278–279 downloading JavaScript, 94–95 AND logical operator (JavaScript), 53 event attributes, 29 anonymous JavaScript functions, 68 example of data Submit and fetch, 4–5 Apache Tomcat Java-based server, 231 XMLHttpRequest importance of object, 62 Apple Safari, 63 server-side scripts and PHP used with, 76–77 arguments, passing to functions, 38–39 Ajax frameworks arithmetic operators (JavaScript), 45 ! caution: importance of files and placement, 152 assignment operators (JavaScript), 44, 45 resultXML ! caution: naming global variable “ ”, 171, 175 asynchronous versus synchronous requests, ! caution: on use of global variables, 155, 159 178, 180 advantages, 152–153 attributes (Ajax), 29, 262–263 Ajax tag library, 236–239 autocomplete capability AJAXLib Ajax framework, 170–175 example demonstration site, 8–9 browser-based versus server-side, 152 support for, in Ajax tag library, 236–237 downloadable and free, 182 installing and allowing
  • Javascript Hijacking

    Javascript Hijacking

    JavaScript Hijacking Brian Chess, Yekaterina Tsipenyuk O'Neil, Jacob West {brian, katrina, jacob}@fortifysoftware.com March 12, 2007 Summary An increasing number of rich Web applications, often called Ajax applications, make use of JavaScript as a data transport mechanism. This paper describes a vulnerability we term JavaScript Hijacking, which allows an unauthorized party to read confidential data contained in JavaScript messages. The attack works by using a <script> tag to circumvent the Same Origin Policy enforced by Web browsers. Traditional Web applications are not vulnerable because they do not use JavaScript as a data transport mechanism. We analyzed 12 popular Ajax frameworks, including 4 server-integrated toolkits – Direct Web Remoting (DWR), Microsoft ASP.NET Ajax (a.k.a. Atlas), xajax and Google Web Toolkit (GWT) -- and 8 purely client-side libraries -- Prototype, Script.aculo.us, Dojo, Moo.fx, jQuery, Yahoo! UI, Rico, and MochiKit. We determined that among them only DWR 2.0 implements mechanisms for preventing JavaScript Hijacking. The rest of the frameworks do not explicitly provide any protection and do not mention any security concerns in their documentation. Many programmers are not using any of these frameworks, but based on our findings with the frameworks, we believe that many custom-built applications are also vulnerable. An application may be vulnerable if it: • Uses JavaScript as a data transfer format • Handles confidential data We advocate a two-pronged mitigation approach that allows applications to decline malicious requests and prevent attackers from directly executing JavaScript the applications generate. 1. Introduction Although the term “Web 2.0” does not have a rigorous definition, it is commonly used in at least two ways.
  • Rewriteengine on # Libwww-Perl Access Fix # Rewritecond

    Rewriteengine on # Libwww-Perl Access Fix # Rewritecond

    # RewriteEngine On # Libwww-perl Access Fix # RewriteCond %{HTTP_USER_AGENT} libwww-perl.* # RewriteRule .* – [F,L] # Redirect www to non-www # RewriteEngine On # RewriteBase / # RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC] # RewriteRule ^(.*)$ http://%1/$1 [R=301,L] # Turn eTags Off # https://github.com/ucarmetin/toolbox/blob/master/lists/awesome-htaccess.md#turn-etags- off # <IfModule mod_headers.c> # Header unset ETag # </IfModule> # FileETag None # BEGIN GZIP <ifmodule mod_deflate.c> AddType x-font/otf .otf AddType x-font/ttf .ttf AddType x-font/eot .eot AddType x-font/woff .woff AddType x-font/woff2 .woff2 AddType image/x-icon .ico AddType image/png .png AddType text/css .css AddType image/svg+xml .svg AddOutputFilterByType DEFLATE text/text text/html text/plain text/xml text/css application/x-javascript application/javascript image/svg+xml x-font/otf x-font/ttf x- font/eot x-font/woff x-font/woff2 image/x-icon image/png </ifmodule> # END GZIP # BEGIN Cache-Control Headers <ifModule mod_headers.c> <filesMatch "\.(ico|jpe?g|png|gif|swf)$"> Header set Cache-Control "public" Header set Cache-Control "public" </filesMatch> <filesMatch "\.(css)$"> Header set Cache-Control "public" </filesMatch> <filesMatch "\.(js)$"> Header set Cache-Control "private" </filesMatch> <filesMatch "\.(x?html?|php)$"> Header set Cache-Control "private, must-revalidate" </filesMatch> </ifModule> # END Cache-Control Headers # Proper MIME Types <IfModule mod_mime.c> # Audio AddType audio/mp4 m4a f4a f4b AddType audio/ogg oga ogg # JavaScript AddType application/javascript
  • Web Browser Frequently Asked Questions (FAQ)

    Web Browser Frequently Asked Questions (FAQ)

    Web Browser Frequently Asked Questions (FAQ) Avaya™ IP Telephone Interface Release 2.2 for 4610SW, 4620/4620SW, 4621SW, and 4622SW IP Telephones Release 2.5 for the 4625SW IP Telephone Issue 2.5 April 2005 Copyright 2005, Avaya Inc. • Theft (such as, of intellectual property, financial assets, or toll All Rights Reserved facility access) Notice • Eavesdropping (privacy invasions to humans) Every effort was made to ensure that the information in this • Mischief (troubling, but apparently innocuous, tampering) document was complete and accurate at the time of printing. However, information is subject to change. • Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions Trademarks associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a DEFINITY is a registered trademark of Avaya, Inc. MultiVantage variety of losses to your company (including but not limited to, is a trademark of Avaya, Inc. HTTP Server functionality is human/data privacy, intellectual property, material assets, financial provided by the GoAhead WebServer 2.1, Copyright © 2004 resources, labor costs, and/or legal costs). GoAhead Software, Inc. All Rights Reserved. Responsibility for Your Company’s Telecommunications Disclaimer Security Avaya is not responsible for any modifications, additions or The final responsibility for securing both this system and its deletions to the original published version of this documentation networked equipment rests with you - Avaya’s customer system unless such modifications, additions or deletions were performed administrator, your telecommunications peers, and your managers.
  • Ajax, State of The

    Ajax, State of The

    AjAjaax,x, ststaattee ooff tthhee aarrtt Tarek Ziadé, Nuxeo [email protected] WWhhoo aamm ii ● I am engineer at Nuxeo ● I work on CPS, the famous ECM Plateform ;) ● I©ve been lately in charge of Ajax stuff in CPS ● I read Ajax related feeds before I go to bed WWhhaatt iiss AAjjaaxx ?? A dutch football club (a good one) A cleanser (really works) AA WWeebb 22..00 tteechchnnoollooggyy Asynchronous Javascript And XML WWhhaatt©©ss WWeebb 22..00 ?? TTiimm OO©©RReeiillllyy©©ss ©©ccoommppaacctt©© ddeeffiinniittiioonn:: Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an "architecture of participation," and going beyond the page metaphor of Web 1.0 to deliver rich user experiences. MMaarrkkuuss AAnnggeerrmmeeiieerr©©ss vviieeww ooff WWeebb 22..00:: (courtesy of Markus Angermeier) WWeebb 22..00 AAppppss ✔ del.icio.us ✔ flickr ✔ Voo2do ✔ Digg ✔ Google Mail (Gmail) ✔ Writely ✔ Basecamp ✔ ... AjAjaaxx bbiigg ppiictctuurere 11//22 (courtesy of J. J. Garett) AjAjaaxx bbiigg ppiictctuurere 22//22 (courtesy of J. J. Garett) TThhee LLiistst ooff tthhiinnggss AjAjaaxx rereaallllyy bbririnnggss ✔ Increases interactivity ✔ Save bandwidth ✔ Helps avoiding some interactive
  • Working with Html, Css, and Http

    Working with Html, Css, and Http

    Chapter 2 WORKING WITH HTML, CSS, AND HTTP Working with HTML An essential aspect of running a website is creating HTML files. Even sites that rely heavily on page technologies other than static HTML, such as script-driven pages, inevitably keep many static HTML files on the site. Although Web authors can write HTML in any text editor, many have adopted specialized HTML editor programs to handle the job. Ideally, an HTML editor should manage the job of converting an authors writing into the structures defined by the HTML standard without requiring the author to know the details of that standard. As the job is accomplished, the editor program may carry out additional tasks, such as letting the author fine-tune the finished documents appearance or handling site management tasks such as uploading documents to a server and checking its links. The most widely used HTML editors handle these secondary tasks with great success. Over the years, however, many designers created their actual HTML code with an emphasis on appearance rather than structure. This so-called presentational markup achieved popularity with an older generation of browsers because no widely supported alternative to controlling an HTML documents appearance was available. Presentational HTML has drawbacks, though, and a growing number of Web authors are abandoning it in favor of HTML markup that describes a documents structure. Reasons for this choice include: Library Technology Reports Many aspects of presentational markup make assumptions about the users display environment (specifically, screen resolution and window width) that are increasingly unwarranted and may lead to accessibility problems.