Skip to content
Audit Complete

Results for https://apachetoday.com

Visit site
United States United States · Santa Clara Completed: Apr 21, 2026 20:47 UTC
Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

HSTS · 1596 peers
You 72
·
Avg 74
At average
0 50 100
Better than 23% of HSTS sites See full HSTS benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

13 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
4

5 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
5

7 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fapachetoday.com)](https://beavercheck.com/results/1dd60185-64d7-4b48-9d8f-34a0b4163f2d)
<a href="https://beavercheck.com/results/1dd60185-64d7-4b48-9d8f-34a0b4163f2d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fapachetoday.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fapachetoday.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
3 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 6 warning

9 barrier(s) likely increasing bounce by ~37%.

Trust (2)

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

13 form field(s) without a label

+6% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (3)

7 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€495 investment → €0.08/month returns + EUR 20,500,000 risk avoided

Payback period: > 2 years First-year ROI: -100%

Investment

€495

6h · 5 findings

Monthly returns

€0.08 /mo

~€0.91 / year

  • Bandwidth savings €0.08

Regulatory risk avoided

EUR 20,500,000

if kept compliant

  • DSGVO EUR 20,000,000
  • EAA EUR 500,000

€90 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€495

5.5 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins
€90 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€1,708,333 / month at risk

~€20,500,001 / year if left unfixed

Compliance Risk

€20,500,000

DSGVOEAA
  • No privacy policy link detected
    DSGVO: EUR 10,000 – EUR 20,000,000
  • Privacy Policy not detected
    DSGVO: EUR 10,000 – EUR 20,000,000
  • No <main> landmark found
    EAA: EUR 1,000 – EUR 500,000

+5 more

Bandwidth Waste

€0.08 /mo

1023.8 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~102 KB per page load
    Saves €0.08/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
36
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
69
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.82 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.97 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.83 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.97 s

Detailed Report

Audit breakdown by category with detailed findings.

98

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
body > center > a > img body > center > a > img
/RealMedia/ads/Creatives/Covalent_Technologies_4a/new_ERS...
Be proactive with SiteScope. FREE trial today. tr > td > a > img
apachetoday.com/RealMedia/ads/Creatives/Mercury_Interactive_2b/SSeyes125x800.gif
td > center > a > img td > center > a > img
/RealMedia/ads/Creatives/Covalent_Technologies_4b/new_ERS...
Linux Today td > center > p > img
linuxtoday.com/pics/ltnet.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Time to Interactive 2.0 s
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 333 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.6 s
Avoid long main-thread tasks 2 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 160 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 310 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
36

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Breaking News td > a > font > b
Preferences td > a > font > b
Contribute td > a > font > b
About td > a > font > b
Apache Module Registry tr > td > font > b
ApacheCon tr > td > font > b
Apache-Perl Integration Project tr > td > font > b
The Java Apache Project tr > td > font > b
PHP Server Side Scripting tr > td > font > b
The Apache FAQ tr > td > font > b
Apache Project tr > td > font > b
The Jakarta Project tr > td > font > b
About Triggers td > a > font > b
Media Kit td > a > font > b
Security td > a > font > b
Triggers td > a > font > b
Login td > a > font > b

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > center > img body > center > img
tbody > tr > td > img tbody > tr > td > img
tbody > tr > td > img tbody > tr > td > img
tr > td > center > img tr > td > center > img
tr > td > center > img tr > td > center > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
td > form > font > input td > form > font > input
td > form > font > input td > form > font > input
form > p > font > input form > p > font > input
tbody > tr > td > input tbody > tr > td > input
tbody > tr > td > input tbody > tr > td > input
tr > td > form > input tr > td > form > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Right Now Yesterday 2 Days Ago 3 Days Ago 4 Days Ago 5 Days Ago 6 Days Ago 1 We… tr > td > font > select#LTTimeframe
Date Reverse Date Reads Reverse Reads Talkback Rev. Talkback tr > td > font > select#LTSortOpt

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > center > a body > center > a
tbody > tr > td > a tbody > tr > td > a
tr > td > center > a tr > td > center > a
tr > td > center > a tr > td > center > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Be proactive with SiteScope. FREE trial today. tbody > tr > td > a
form > p > font > input form > p > font > input
Right Now Yesterday 2 Days Ago 3 Days Ago 4 Days Ago 5 Days Ago 6 Days Ago 1 We… tr > td > font > select#LTTimeframe
Date Reverse Date Reads Reverse Reads Talkback Rev. Talkback tr > td > font > select#LTSortOpt
-= Highlighted stories above -- Normal news below =- tr > td > center > a
tr > td > form > input tr > td > form > input

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Planet Linux Today Linux Central PHPBuilder Linux Apps Apache Today Just … tbody > tr > td > table
Apache Module Registry ApacheCon Apache-Perl Integration Project The Java Apach… tbody > tr > td > table

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Planet Linux Today Linux Central PHPBuilder Linux Apps Apache Today Just … tbody > tr > td > table
Apache Module Registry ApacheCon Apache-Perl Integration Project The Java Apach… tbody > tr > td > table
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Input buttons have discernible text.
Document has a `<title>` element
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
69

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
ss.webring.yahoo.com/navbar?f=j&y=paulmferris&u=97084277210026050Blocked
linuxtoday.com/pics/ltnet.pngAutomatically upgraded to HTTPS
linuxcentral.com/cgi-bin/sredAllowed with warning
e-newsletters.internet.com/cgi-bin/subscribeAllowed with warning
linuxtoday.com/search.php3Allowed with warning

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
td > center > a > img td > center > a > img
apachetoday.com/RealMedia/ads/Creatives/House_ISP_Expo_3x/ispbusexpo_125_new.gif125 x 125125 x 125188 x 188
Apache Today [Your Apache News Source] tr > td > a > img
apachetoday.com/pics/at_logo.png160 x 60160 x 60240 x 90
The Linux Channel at internet.com tbody > tr > td > img
apachetoday.com/pics/logo_osl_inetcom_wtux.png117 x 57117 x 57176 x 86
linuxcentral.com td > center > p > img
apachetoday.com/pics/lc_logo130.png130 x 44130 x 44195 x 66
Apache HTTPD Links tbody > tr > td > img
apachetoday.com/pics/logo_feather.png119 x 34119 x 34179 x 51
tr > td > a > img tr > td > a > img
apachetoday.com/RealMedia/ads/Creatives/default/empty.gif2 x 21 x 13 x 3

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Mixed Content: The page at 'https://apachetoday.com/' was loaded over HTTPS, but requested an insecure script 'http://ss.webring.yahoo.com/navbar?f=j&y=paulmferris&u=97084277210026050'. This request has been blocked; the content must be served over HTTPS.
apachetoday.com/ line 13, col 113
ReferenceError: getCookie is not defined at onload (https://apachetoday.com/:14:114)

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Detected JavaScript libraries
75

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > center > img body > center > img
tbody > tr > td > img tbody > tr > td > img
tbody > tr > td > img tbody > tr > td > img
tr > td > center > img tr > td > center > img
tr > td > center > img tr > td > center > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html>Syntax not understood
3<head>Syntax not understood
4 <title>Apache Today - Apache News for 03/29/2002</title>Syntax not understood
5 <style>Syntax not understood
7 <!--Syntax not understood
8 TD.lcnormal {font-family:arial,helvetica,sans-serif;}Unknown directive
9 A.lcnormal {color:0066FF;}Unknown directive
10 A.lcnormal:hover {color:cc9900;}Unknown directive
11 // -->Syntax not understood
12 </style>Syntax not understood
13</head>Syntax not understood
14<body onload="getCookie('surveyflag')" bgcolor="#FFFFFF" link="#0044DE" text="#002244" vlink="black" alink="red">Syntax not understood
15 <center>Syntax not understood
16 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/877874199/468x60-1/Covalent_Technologies_4a/new_ERS_seminar_750x100.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/Covalent_Technologies_4a/new_ERS_seminar_750x100.gif" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/877874199/468x60-1/Covalent_Technologies_4a/new_ERS_seminar_750x100.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
17 <center>Syntax not understood
18 <table border="0" width="100%">Syntax not understood
19 <tr>Syntax not understood
20 <td align="left"><font size="-1">Your Daily Source for Apache News and Information</font></td>Syntax not understood
21 <td align="center">&nbsp;</td>Syntax not understood
22 <td align="right">Syntax not understood
23 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/1287080011/sitetext-1/default/empty.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/default/empty.gif" width="2" height="2" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/1287080011/sitetext-1/default/empty.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
24 </td>Syntax not understood
25 </tr>Syntax not understood
26 </table>Syntax not understood
27 <table bgcolor="#0044DE" width="100%">Syntax not understood
28 <tr align="center">Syntax not understood
29 <td bgcolor="#999900">Syntax not understood
30 <a href="/"><font color="#FFFFFF"><b>Breaking News</b></font></a>Syntax not understood
31 </td>Syntax not understood
32 <td bgcolor="#00BB44">Syntax not understood
33 <a href="/preferences.php3"><font color="#FFFFFF"><b>Preferences</b></font></a>Syntax not understood
34 </td>Syntax not understood
35 <td bgcolor="#009999">Syntax not understood
36 <a href="/contribute.php3"><font color="#FFFFFF"><b>Contribute</b></font></a>Syntax not understood
37 </td>Syntax not understood
38 <td bgcolor="#0044DD">Syntax not understood
39 <a href="/trigger.php3"><font color="#FFFFFF"><b>Triggers</b></font></a>Syntax not understood
40 </td>Syntax not understood
41 <td bgcolor="#3300FF">Syntax not understood
42 <a href="/linkus.php3"><font color="#FFFFFF"><b>Link Us</b></font></a>Syntax not understood
43 </td>Syntax not understood
44 <td bgcolor="#9900FF">Syntax not understood
45 <a href="/search.php3"><font color="#FFFFFF"><b>Search</b></font></a>Syntax not understood
46 </td>Syntax not understood
47 <td bgcolor="#FF0099">Syntax not understood
48 <a href="/about.php3"><font color="#FFFFFF"><b>About</b></font></a>Syntax not understood
49 </td>Syntax not understood
50 </tr>Syntax not understood
51 </table>Syntax not understood
52 <p></p>Syntax not understood
53 <table border="0" width="100%" cellpadding="6" cellspacing="0">Syntax not understood
54 <tr>Syntax not understood
55 <td width="130" valign="top">Syntax not understood
56 <a href="/"><img height="60" width="160" src="/pics/at_logo.png" border="0" alt="Apache Today [Your Apache News Source]"></a> <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/923878324/125x800/Mercury_Interactive_2b/SSeyes125x800.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/Mercury_Interactive_2b/SSeyes125x800.gif" alt="Be proactive with SiteScope. FREE trial today." border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/923878324/125x800/Mercury_Interactive_2b/SSeyes125x800.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0"><br>Syntax not understood
57 <table border="0" cellpadding="0" cellspacing="4" width="120">Syntax not understood
58 <tr bgcolor="#FFFFFF">Syntax not understood
59 <td align="center">Syntax not understood
60 <img src="/pics/logo_osl_inetcom_wtux.png" width="117" height="57" border="0" alt="The Linux Channel at internet.com" vspace="3"><br>Syntax not understood
61 <table border="0" width="100%">Syntax not understood
62 <tr>Syntax not understood
63 <td colspan="3"><font size="-1">Linux&nbsp;Planet</font></td>Syntax not understood
64 </tr>Syntax not understood
65 <tr>Syntax not understood
66 <td colspan="3"><font size="-1">Linux&nbsp;Today</font></td>Syntax not understood
67 </tr>Syntax not understood
68 <tr>Syntax not understood
69 <td colspan="3"><font size="-1">Linux&nbsp;Central</font></td>Syntax not understood
70 </tr>Syntax not understood
71 <tr>Syntax not understood
72 <td colspan="3"><font size="-1">PHPBuilder</font></td>Syntax not understood
73 </tr>Syntax not understood
74 <tr>Syntax not understood
75 <td colspan="3"><font size="-1">Linux&nbsp;Apps</font></td>Syntax not understood
76 </tr>Syntax not understood
77 <tr>Syntax not understood
78 <td colspan="3">Syntax not understood
79 <a href="/"><font size="-1">Apache&nbsp;Today</font></a>Syntax not understood
80 </td>Syntax not understood
81 </tr>Syntax not understood
82 <tr>Syntax not understood
83 <td colspan="3"><font size="-1">Just&nbsp;Linux</font></td>Syntax not understood
84 </tr>Syntax not understood
85 <tr>Syntax not understood
86 <td colspan="3"><font size="-1">Linux&nbsp;Programming</font></td>Syntax not understood
87 </tr>Syntax not understood
88 <tr>Syntax not understood
89 <td colspan="3"><font size="-1">BSD&nbsp;Today</font></td>Syntax not understood
90 </tr>Syntax not understood
91 <tr>Syntax not understood
92 <td colspan="3"><font size="-1">All&nbsp;Linux Devices</font></td>Syntax not understood
93 </tr>Syntax not understood
94 <tr>Syntax not understood
95 <td colspan="3"><font size="-1">Enterprise Linux&nbsp;Today</font></td>Syntax not understood
96 </tr>Syntax not understood
97 <tr>Syntax not understood
98 <td colspan="3"><font size="-1">Linuxnewbie.org</font></td>Syntax not understood
99 </tr>Syntax not understood
100 <tr>Syntax not understood
101 <td colspan="3"><font size="-1">BSD&nbsp;Central</font></td>Syntax not understood
102 </tr>Syntax not understood
103 <tr>Syntax not understood
104 <td colspan="3"><font size="-1">Linux&nbsp;Start</font></td>Syntax not understood
105 </tr>Syntax not understood
106 <tr align="center" bgcolor="#0044DE">Syntax not understood
107 <td><font size="1"><font color="#FFFFFF">SITE DESCRIPTIONS</font></font></td>Syntax not understood
108 </tr>Syntax not understood
109 </table>Syntax not understood
110 </td>Syntax not understood
111 </tr>Syntax not understood
112 </table>Syntax not understood
113 <table cellspacing="0" cellpadding="0" width="130" border="0">Syntax not understood
114 <tr>Syntax not understood
115 <td bgcolor="#EEEEEE" height="2" colspan="2" width="130">Syntax not understood
116 <hr noshade>Syntax not understood
117 </td>Syntax not understood
118 </tr>Syntax not understood
119 <tr>Syntax not understood
120 <td bgcolor="#EEEEEE" width="5">&nbsp;</td>Syntax not understood
121 <td bgcolor="#EEEEEE"><font color="#333333" size="-1"><b>internet.com</b></font><br>Syntax not understood
122 <font color="#333333" size="-1"><br>Syntax not understood
123 Internet News<br>Syntax not understood
124 Internet Investing<br>Syntax not understood
125 Internet Technology<br>Syntax not understood
126 Windows Internet Tech.<br>Syntax not understood
127 Linux/Open Source<br>Syntax not understood
128 Web Developer<br>Syntax not understood
129 ECommerce/Marketing<br>Syntax not understood
130 ISP Resources<br>Syntax not understood
131 ASP Resources<br>Syntax not understood
132 Wireless Internet<br>Syntax not understood
133 Downloads<br>Syntax not understood
134 Internet Resources<br>Syntax not understood
135 Internet Lists<br>Syntax not understood
136 International<br>Syntax not understood
137 EarthWeb<br>Syntax not understood
138 Career Resources<br>Syntax not understood
139 <br>Syntax not understood
140 Search internet.com<br>Syntax not understood
141 Advertising Info<br>Syntax not understood
142 Corporate Info<br></font></td>Syntax not understood
143 </tr>Syntax not understood
144 </table>Syntax not understood
145 <p></p>Syntax not understood
146 <table border="0" cellpadding="0" cellspacing="0" width="130">Syntax not understood
147 <tr bgcolor="#FFFFFF">Syntax not understood
148 <td align="center">Syntax not understood
149 <img src="/pics/logo_feather.png" width="119" height="34" border="0" alt="Apache HTTPD Links" vspace="0"><br>Syntax not understood
150 <table border="0" cellpadding="0" cellspacing="0" width="100%">Syntax not understood
151 <tr>Syntax not understood
152 <td colspan="3"><font size="-1" color="#FF0022"><b>Apache Module Registry</b></font></td>Syntax not understood
153 </tr>Syntax not understood
154 <tr>Syntax not understood
155 <td colspan="3"><font size="-1" color="#FF3300"><b>ApacheCon</b></font></td>Syntax not understood
156 </tr>Syntax not understood
157 <tr>Syntax not understood
158 <td colspan="3"><font size="-1" color="#DD7400"><b>Apache-Perl Integration Project</b></font></td>Syntax not understood
159 </tr>Syntax not understood
160 <tr>Syntax not understood
161 <td colspan="3"><font size="-1" color="#999900"><b>The Java Apache Project</b></font></td>Syntax not understood
162 </tr>Syntax not understood
163 <tr>Syntax not understood
164 <td colspan="3"><font size="-1" color="#00BB44"><b>PHP Server Side Scripting</b></font></td>Syntax not understood
165 </tr>Syntax not understood
166 <tr>Syntax not understood
167 <td colspan="3"><font size="-1" color="#009999"><b>The Apache FAQ</b></font></td>Syntax not understood
168 </tr>Syntax not understood
169 <tr>Syntax not understood
170 <td colspan="3"><font size="-1" color="#0044DD"><b>Apache XML Project</b></font></td>Syntax not understood
171 </tr>Syntax not understood
172 <tr>Syntax not understood
173 <td colspan="3"><font size="-1" color="#3300FF"><b>Apache-Related Projects</b></font></td>Syntax not understood
174 </tr>Syntax not understood
175 <tr>Syntax not understood
176 <td colspan="3"><font size="-1" color="#9900FF"><b>The Apache Software Foundation</b></font></td>Syntax not understood
177 </tr>Syntax not understood
178 <tr>Syntax not understood
179 <td colspan="3"><font size="-1" color="#FF0099"><b>Apache Project</b></font></td>Syntax not understood
180 </tr>Syntax not understood
181 <tr>Syntax not understood
182 <td colspan="3"><font size="-1" color="#FF0022"><b>The Jakarta Project</b></font></td>Syntax not understood
183 </tr>Syntax not understood
184 </table>Syntax not understood
185 </td>Syntax not understood
186 </tr>Syntax not understood
187 </table>Syntax not understood
188 <p></p>Syntax not understood
189 <table bgcolor="#000000" border="0" width="140">Syntax not understood
190 <tr>Syntax not understood
191 <td>Syntax not understood
192 <table cellspacing="1" cellpadding="4" bgcolor="#FFFFFF" border="0" width="100%">Syntax not understood
193 <tr>Syntax not understood
194 <td valign="middle" align="center" bgcolor="#EEEEEE"><font color="#000000" face="arial,helvetica,sans-serif"><b>linuxcentral.com: New Products</b></font></td>Syntax not understood
195 </tr>Syntax not understood
196 <tr>Syntax not understood
197 <td>Syntax not understood
198 <center>Syntax not understood
199 <p><img src="/pics/lc_logo130.png" alt="linuxcentral.com" border="0" width="130" height="44"></p>Syntax not understood
200 </center>Syntax not understood
201 <p>"<font face="arial,helvetica,sans-serif">Mandrake Linux ProSuite Edition 8.2 (PRE-ORDER)</font><br>Syntax not understood
202 "<font face="arial,helvetica,sans-serif">Mandrake Linux PowerPack Edition 8.2 (PRE-ORDER)</font><br>Syntax not understood
203 "<font face="arial,helvetica,sans-serif">Linux Administration: A Beginner's Guide</font><br>Unknown directive
204 "<font face="arial,helvetica,sans-serif">BRU Pro 2.0</font><br>Syntax not understood
205 "<font face="arial,helvetica,sans-serif">Building Linux Virtual Private Networks (VPNs)</font><br>Syntax not understood
206 "<font face="arial,helvetica,sans-serif">Linux Routing</font><br>Syntax not understood
207 "<font face="arial,helvetica,sans-serif">Mandrake Linux 8.2 (3 CD set) PRE-ORDER</font><br>Syntax not understood
208 "<font face="arial,helvetica,sans-serif">The Book of VMware</font><br>Syntax not understood
209 "<font face="arial,helvetica,sans-serif">Quanta Gold</font><br>Syntax not understood
210 "<font face="arial,helvetica,sans-serif">Rekall</font><br></p>Syntax not understood
211 <form method="get" action="http://linuxcentral.com/cgi-bin/sred">Unknown directive
212 <font size="2" face="arial,helvetica,sans-serif"><b>Search for Linux products</b><br>Syntax not understood
213 <input type="text" name="s_prod_name" size="15"><br></font>Syntax not understood
214 </form>Syntax not understood
215 </td>Syntax not understood
216 </tr>Syntax not understood
217 </table>Syntax not understood
218 </td>Syntax not understood
219 </tr>Syntax not understood
220 </table>Syntax not understood
221 <p></p>Syntax not understood
222 <center>Syntax not understood
223 Serverwatch<br>Syntax not understood
224 NewsletterSyntax not understood
225 </center>Syntax not understood
226 <table align="center" border="0">Syntax not understood
227 <tr>Syntax not understood
228 <td>Syntax not understood
229 <font size="-1"></font>Syntax not understood
230 <form action="http://e-newsletters.internet.com/cgi-bin/subscribe" method="post">Unknown directive
231 <font size="-1"><br>Syntax not understood
232 <input type="checkbox" name="List_Name" value="serverwatch-text"> Subscribe News<br></font>Syntax not understood
233 <p><font size="-1"><input type="text" name="email" size="20" value="enter email"> <input type="submit" name="Submit" value="Submit"></font></p>Syntax not understood
234 </form>Syntax not understood
235 </td>Syntax not understood
236 </tr>Syntax not understood
237 </table>Syntax not understood
238 </td>Syntax not understood
239 <td valign="top">Syntax not understood
240 <form name="TIMEFRAME" action="/index.php3" method="get" id="TIMEFRAME">Syntax not understood
241 <table width="99%" border="0" cellspacing="0" cellpadding="0">Syntax not understood
242 <tr valign="middle" align="center">Syntax not understood
243 <td>Time Frame</td>Syntax not understood
244 <td>Sort Order</td>Syntax not understood
245 <td>View</td>Syntax not understood
246 </tr>Syntax not understood
247 <tr valign="middle" align="center">Syntax not understood
248 <td><font size="-2"><select id="LTTimeframe" name="LTD">Syntax not understood
249 <option value="Now" selected>Syntax not understood
250 Right NowSyntax not understood
251 </option>Syntax not understood
252 <option value="Day-1">Syntax not understood
253 YesterdaySyntax not understood
254 </option>Syntax not understood
255 <option value="Day-2">Syntax not understood
256 2 Days AgoSyntax not understood
257 </option>Syntax not understood
258 <option value="Day-3">Syntax not understood
259 3 Days AgoSyntax not understood
260 </option>Syntax not understood
261 <option value="Day-4">Syntax not understood
262 4 Days AgoSyntax not understood
263 </option>Syntax not understood
264 <option value="Day-5">Syntax not understood
265 5 Days AgoSyntax not understood
266 </option>Syntax not understood
267 <option value="Day-6">Syntax not understood
268 6 Days AgoSyntax not understood
269 </option>Syntax not understood
270 <option value="Day-7">Syntax not understood
271 1 Week AgoSyntax not understood
272 </option>Syntax not understood
273 </select></font></td>Syntax not understood
274 <td><font size="-2"><select id="LTSortOpt" name="LTS">Syntax not understood
275 <option value="Ftimestamp">Syntax not understood
276 DateSyntax not understood
277 </option>Syntax not understood
278 <option value="Rtimestamp">Syntax not understood
279 Reverse DateSyntax not understood
280 </option>Syntax not understood
281 <option value="Freads">Syntax not understood
282 ReadsSyntax not understood
283 </option>Syntax not understood
284 <option value="Rreads">Syntax not understood
285 Reverse ReadsSyntax not understood
286 </option>Syntax not understood
287 <option value="Ftalkback">Syntax not understood
288 TalkbackSyntax not understood
289 </option>Syntax not understood
290 <option value="Rtalkback">Syntax not understood
291 Rev. TalkbackSyntax not understood
292 </option>Syntax not understood
293 </select></font></td>Syntax not understood
294 <td><font size="-2"><input type="submit" value="Update"></font></td>Syntax not understood
295 </tr>Syntax not understood
296 </table>Syntax not understood
297 </form>Syntax not understood
298 <center>Syntax not understood
299 <a name="highnews" id="highnews">&nbsp;</a><a href="/preferences.php3?area=topichigh">-= Highlighted stories above -- Normal news below =-</a>Syntax not understood
300 </center>Syntax not understood
301 <p></p>Syntax not understood
302 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
303 <tr>Syntax not understood
304 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
305 <a href="/story/2002-03-26-002-06-PS-PL-AD.html"><font size="4" face="arial,helvetica">perl.com: mod_perl in 30 minutes</font></a>Unknown directive
306 </td>Syntax not understood
307 </tr>Syntax not understood
308 </table><font size="1">(Mar 26, 2002, 19:43 UTC) (478 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
309 <font size="+0" face="arial,helvetica">"mod_perl in 30 minutes" article updated for apache_1.3.20 and mod_perl-1.26.</font>Syntax not understood
310 <p></p>Syntax not understood
311 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
312 <tr>Syntax not understood
313 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
314 <a href="/story/2002-03-26-001-06-PS-CY.html"><font size="4" face="arial,helvetica">Sun to allow open source Java implementations</font></a>Syntax not understood
315 </td>Syntax not understood
316 </tr>Syntax not understood
317 </table><font size="1">(Mar 26, 2002, 16:00 UTC) (723 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
318 <font size="+0" face="arial,helvetica">The Apache Software Foundation today announced that it has reached an agreement with Sun Microsystems and members of the Java Community Process to secure the basic right to implement Java specifications in open source.</font>Syntax not understood
319 <p></p>Syntax not understood
320 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
321 <tr>Syntax not understood
322 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
323 <a href="/story/2002-03-22-001-06-SC-CY-AD.html"><font size="4" face="arial,helvetica">SECURITY: Vulnerability in Apache for Win32 batch file processing</font></a>Unknown directive
324 </td>Syntax not understood
325 </tr>Syntax not understood
326 </table><font size="1">(Mar 22, 2002, 17:29 UTC) (1007 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
327 <font size="+0" face="arial,helvetica">Apache 1.3.24 was released. It fixes a remote command execution vulnerability.</font>Syntax not understood
328 <p></p>Syntax not understood
329 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
330 <tr>Syntax not understood
331 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
332 <a href="/story/2002-03-20-001-06-PS-PL.html"><font size="4" face="arial,helvetica">WebReference.com: mod_perl Developer's Cookbook</font></a>Unknown directive
333 </td>Syntax not understood
334 </tr>Syntax not understood
335 </table><font size="1">(Mar 20, 2002, 15:50 UTC) (895 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
336 <font size="+0" face="arial,helvetica">WebReference.com has published Chapter 4 from the newly released mod_perl Developer's Cookbook.</font>Syntax not understood
337 <p></p>Syntax not understood
338 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
339 <tr>Syntax not understood
340 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
341 <a href="/story/2002-03-13-002-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">mod_l33t added to Apache Module Registry</font></a>Syntax not understood
342 </td>Syntax not understood
343 </tr>Syntax not understood
344 </table><font size="1">(Mar 13, 2002, 21:09 UTC) (2799 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
345 <font size="+0" face="arial,helvetica">mod_l33t is a fast, memory-efficient, dynamic, and limited virtual hosting module for Apache.</font>Syntax not understood
346 <p></p>Syntax not understood
347 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
348 <tr>Syntax not understood
349 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
350 <a href="/story/2002-03-13-001-06-OS-SW-PH.html"><font size="4" face="arial,helvetica">Linux Easy Installer - Security Fixes</font></a>Syntax not understood
351 </td>Syntax not understood
352 </tr>Syntax not understood
353 </table><font size="1">(Mar 13, 2002, 21:02 UTC) (1571 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
354 <font size="+0" face="arial,helvetica">Linux Easy Installer package has been update to resolve upload PHP security problem.</font>Syntax not understood
355 <p></p>Syntax not understood
356 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
357 <tr>Syntax not understood
358 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
359 <a href="/story/2002-03-06-001-06-PS-DT-AD.html"><font size="4" face="arial,helvetica">Daemon News: Jakarta-Tomcat on FreeBSD 4.4</font></a>Unknown directive
360 </td>Syntax not understood
361 </tr>Syntax not understood
362 </table><font size="1">(Mar 6, 2002, 17:21 UTC) (3968 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
363 <font size="+0" face="arial,helvetica">"Servlets are small Java programs and are a better way to handle CGI tasks such as dynamic content and database interaction. Servlets run inside the Java Virtual Machine, which handles threads for each new request instead of the per instance model of traditional CGI programs. ... Tomcat is The Apache Group's reference implementation of a Servlet engine. It can handle both Servlets and JSPs. Tomcat can be run in stand-alone mode or with a HTTP server, such as Apache."</font>Syntax not understood
364 <p></p>Syntax not understood
365 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
366 <tr>Syntax not understood
367 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
368 <a href="/story/2002-03-05-001-06-OS-DT-PH.html"><font size="4" face="arial,helvetica">Moto, a compilable server-side scripting language</font></a>Syntax not understood
369 </td>Syntax not understood
370 </tr>Syntax not understood
371 </table><font size="1">(Mar 5, 2002, 01:05 UTC) (3357 reads) (2 talkbacks) (Posted by )</font><br>Unknown directive
372 <font size="+0" face="arial,helvetica">Moto is an embedded server-side scripting language first released about a year ago. Over the last few months, Moto has been undergoing heavy development. It has been ported to a wide variety of Unix platforms, including Mac OS X, Solaris, and FreeBSD, in addition to the many flavors of Linux it already ran on.</font>Syntax not understood
373 <p></p>Syntax not understood
374 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
375 <tr>Syntax not understood
376 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
377 <a href="/story/2002-03-01-001-06-SC-PH-AD.html"><font size="4" face="arial,helvetica">SECURITY: Flaws Found in PHP Leave Web Servers Open to Attack</font></a>Unknown directive
378 </td>Syntax not understood
379 </tr>Syntax not understood
380 </table><font size="1">(Mar 1, 2002, 18:56 UTC) (4145 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
381 <font size="+0" face="arial,helvetica">The Computer Emergency Response Team Coordination Center (CERT/CC) Wednesday warned of multiple vulnerabilities in the PHP scripting language that allow a remote attacker to execute arbitrary code with the privileges of the PHP process on a victim's system.</font>Syntax not understood
382 <p></p>Syntax not understood
383 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
384 <tr>Syntax not understood
385 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
386 <a href="/story/2002-02-26-002-06-PS-DP-AD.html"><font size="4" face="arial,helvetica">Everything Solaris: Apache: Handling Traffic</font></a>Unknown directive
387 </td>Syntax not understood
388 </tr>Syntax not understood
389 </table><font size="1">(Feb 26, 2002, 04:41 UTC) (4935 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
390 <font size="+0" face="arial,helvetica">"How you scale your infrastructure from here is wholly dependant on your growth needs and budget available. You will need to analyze your Website traffic and monitor your server performance characteristics closely to see how they all interelate."</font>Syntax not understood
391 <p></p>Syntax not understood
392 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
393 <tr>Syntax not understood
394 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
395 <a href="/story/2002-02-26-001-06-NW-CY-PH.html"><font size="4" face="arial,helvetica">LinuxEasyInstaller 2.0 final release</font></a>Syntax not understood
396 </td>Syntax not understood
397 </tr>Syntax not understood
398 </table><font size="1">(Feb 26, 2002, 04:36 UTC) (5545 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
399 <font size="+0" face="arial,helvetica">Linux Easy Installer is a script written in Perl that allows you to install quickly Apache, PHP, MySQL and phpMyAdmin. This script contains the sources of the programs, make the install and modify the configuration file.</font>Syntax not understood
400 <p></p>Syntax not understood
401 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
402 <tr>Syntax not understood
403 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
404 <a href="/story/2002-02-19-002-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Apache 2.0.32 beta is available</font></a>Syntax not understood
405 </td>Syntax not understood
406 </tr>Syntax not understood
407 </table><font size="1">(Feb 19, 2002, 23:31 UTC) (5261 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
408 <font size="+0" face="arial,helvetica">"The Apache HTTP Server Project is proud to announce the thirty-second release of Apache 2.0. The Apache HTTP Server Project has determined that this release is of beta quality. This makes 2.0.32 the third public beta of Apache 2.0. This release has been tested thoroughly and has been running the apache.org web site since Feb. 7, 2002."</font>Syntax not understood
409 <p></p>Syntax not understood
410 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
411 <tr>Syntax not understood
412 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
413 <a href="/story/2002-02-19-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Everything Solaris: Apache: The Basics</font></a>Unknown directive
414 </td>Syntax not understood
415 </tr>Syntax not understood
416 </table><font size="1">(Feb 19, 2002, 16:43 UTC) (4684 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
417 <font size="+0" face="arial,helvetica">"... In this article, we'll cover the very basics of Apache such as what it is and what it does, getting and installing it and properly configuring it to serve your first pages. Finally, some basic maintenance that you must do to keep everything running smoothly."</font>Syntax not understood
418 <p></p>Syntax not understood
419 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
420 <tr>Syntax not understood
421 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
422 <a href="/story/2002-02-06-003-06-PR-CY.html"><font size="4" face="arial,helvetica">Apache Jakarta James Mailserver v2.0a2 Released</font></a>Syntax not understood
423 </td>Syntax not understood
424 </tr>Syntax not understood
425 </table><font size="1">(Feb 6, 2002, 22:13 UTC) (6179 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
426 <font size="+0" face="arial,helvetica">James is a platform independant Java(tm) email and news server built using the Avalon application framenwork and supporting SMTP, POP3 and NNTP.</font>Syntax not understood
427 <p></p>Syntax not understood
428 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
429 <tr>Syntax not understood
430 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
431 <a href="/story/2002-02-06-002-06-NW-DB-PG.html"><font size="4" face="arial,helvetica">PostgreSQL v7.2 Final Release</font></a>Syntax not understood
432 </td>Syntax not understood
433 </tr>Syntax not understood
434 </table><font size="1">(Feb 6, 2002, 22:06 UTC) (31818 reads) (4 talkbacks) (Posted by )</font><br>Unknown directive
435 <font size="+0" face="arial,helvetica">"After almost a full year of development since PostgreSQL v7.1 was released, the PostgreSQL Global Development Group is proud to announce the availability of our latest development milestone ... PostgreSQL v7.2, another step forward for the project."</font>Syntax not understood
436 <p></p>Syntax not understood
437 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
438 <tr>Syntax not understood
439 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
440 <a href="/story/2002-02-06-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Daemon News: Multiple webservers behind one IP address</font></a>Unknown directive
441 </td>Syntax not understood
442 </tr>Syntax not understood
443 </table><font size="1">(Feb 6, 2002, 19:40 UTC) (8421 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
444 <font size="+0" face="arial,helvetica">"This article discusses a network setup where multiple webservers reside behind one IP address. Such a situation may arise when you need a specific webserver for one task and a different webserver for another task, running different operating systems or webserver software. With only one IP address available from the Internet, you could simply use Network Address Translation (NAT) with port forwarding. However, this forces you to give each webserver an ugly URL with a non-standard port number. Luckily, there is a better way. In the setup described in this article, each webserver can be reached via its own fully qualified domainname on the standard HTTP port (80)."</font>Syntax not understood
445 <p></p>Syntax not understood
446 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
447 <tr>Syntax not understood
448 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
449 <a href="/story/2002-02-04-001-06-PR-DT-AD.html"><font size="4" face="arial,helvetica">Zend Technologies launches Zend Studio 2.0</font></a>Syntax not understood
450 </td>Syntax not understood
451 </tr>Syntax not understood
452 </table><font size="1">(Feb 4, 2002, 18:38 UTC) (4652 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
453 <font size="+0" face="arial,helvetica">The "all-in-one" client-sever development package conveniently integrates all the applications developers need to code, debug and deploy advanced PHP e-commerce and business applications.</font>Syntax not understood
454 <p></p>Syntax not understood
455 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
456 <tr>Syntax not understood
457 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
458 <a href="/story/2002-01-31-001-06-PR-BZ-DT.html"><font size="4" face="arial,helvetica">NuSphere first to enable development of PHP web services</font></a>Syntax not understood
459 </td>Syntax not understood
460 </tr>Syntax not understood
461 </table><font size="1">(Jan 31, 2002, 02:44 UTC) (5506 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
462 <font size="+0" face="arial,helvetica">NuSphere offers integrated support for Apache, Perl, PHP and MySQL. NuSphere's PHPEd is an IDE (Integrated Development Environment) that integrates a comprehensive set of editing, debugging and deployment tools.</font>Syntax not understood
463 <p></p>Syntax not understood
464 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
465 <tr>Syntax not understood
466 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
467 <a href="/story/2002-01-28-001-06-PR-BZ-CY.html"><font size="4" face="arial,helvetica">Covalent Technologies raises $18 million in venture capital</font></a>Syntax not understood
468 </td>Syntax not understood
469 </tr>Syntax not understood
470 </table><font size="1">(Jan 28, 2002, 22:29 UTC) (3915 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
471 <font size="+0" face="arial,helvetica">Covalent Technologies, a leader in enterprise solutions for the Apache Web server, will use funds to expand sales and marketing efforts, and accelerate the company's growth in all business areas, including development of new enterprise management products.</font>Syntax not understood
472 <p></p>Syntax not understood
473 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
474 <tr>Syntax not understood
475 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
476 <a href="/story/2002-01-25-001-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Apache 1.3.23 released</font></a>Syntax not understood
477 </td>Syntax not understood
478 </tr>Syntax not understood
479 </table><font size="1">(Jan 25, 2002, 20:12 UTC) (7484 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
480 <font size="+0" face="arial,helvetica">The Apache Group has released version 1.3.23 of the Apache HTTP webserver. (No security vulnerabilities were addressed in this release.)</font>Syntax not understood
481 <p></p>Syntax not understood
482 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
483 <tr>Syntax not understood
484 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
485 <a href="/story/2002-01-24-001-06-PS-DT-MQ.html"><font size="4" face="arial,helvetica">wdvl: Build Your Own Database Driven Website Using PHP and MySQL: Part 4</font></a>Unknown directive
486 </td>Syntax not understood
487 </tr>Syntax not understood
488 </table><font size="1">(Jan 24, 2002, 18:17 UTC) (7158 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
489 <font size="+0" face="arial,helvetica">Learn how to install PHP and MySQL under Windows or Linux, as well as how to build a live Web-based content management system! This final installment covers publishing MySQL data on the Web, connecting to MySQL with PHP, sending SQL queries with PHP, inserting data into the database, and even has a "homework" assignment. From SitePoint.</font>Syntax not understood
490 <p></p>Syntax not understood
491 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
492 <tr>Syntax not understood
493 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
494 <a href="/story/2002-01-18-001-06-OS-BZ.html"><font size="4" face="arial,helvetica">Business 2.0: Find High Tech in the Bargain Basement</font></a>Unknown directive
495 </td>Syntax not understood
496 </tr>Syntax not understood
497 </table><font size="1">(Jan 18, 2002, 20:29 UTC) (4319 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
498 <font size="+0" face="arial,helvetica">Business 2.0 on Open Source and Apache as a Bargain</font>Syntax not understood
499 <p></p>Syntax not understood
500 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
501 <tr>Syntax not understood
502 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
503 <a href="/story/2002-01-10-001-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Another mod_xslt added to the Apache Module Registry database</font></a>Syntax not understood
504 </td>Syntax not understood
505 </tr>Syntax not understood
506 </table><font size="1">(Jan 10, 2002, 18:33 UTC) (4941 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
507 <font size="+0" face="arial,helvetica">An Apache module for parsing xml with an xsl was added to the Apache Module Registry.</font>Syntax not understood
508 <p></p>Syntax not understood
509 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
510 <tr>Syntax not understood
511 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
512 <a href="/story/2002-01-03-001-06-NW-BZ-CY.html"><font size="4" face="arial,helvetica">Netcraft Web Server Survey for December is available</font></a>Syntax not understood
513 </td>Syntax not understood
514 </tr>Syntax not understood
515 </table><font size="1">(Jan 3, 2002, 22:12 UTC) (5932 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
516 <font size="+0" face="arial,helvetica">Apache continues to be the top used web server with 56.50 percent. Microsoft IIS is used by 30.75 percent, according to the survey. According to Netcraft's research, Apache runs 20,497,607 sites.</font>Syntax not understood
517 <p></p>Syntax not understood
518 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
519 <tr>Syntax not understood
520 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
521 <a href="/story/2001-12-26-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">O'Reilly: Apache Web-Serving with Mac OS X: Part 1</font></a>Unknown directive
522 </td>Syntax not understood
523 </tr>Syntax not understood
524 </table><font size="1">(Dec 26, 2001, 19:26 UTC) (4692 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
525 <font size="+0" face="arial,helvetica">"Most people know that Mac OS X ships with a built-in Apache web server, but don't realize that it's easy to configure and run. In fact, you can host a web site in minutes after completing just a few simple steps. ..."</font>Syntax not understood
526 <p></p>Syntax not understood
527 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
528 <tr>Syntax not understood
529 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
530 <a href="/story/2001-12-14-001-06-PS-AD.html"><font size="4" face="arial,helvetica">WDVL: Perl for Web Site Management: Part 3</font></a>Unknown directive
531 </td>Syntax not understood
532 </tr>Syntax not understood
533 </table><font size="1">(Dec 14, 2001, 17:00 UTC) (4997 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
534 <font size="+0" face="arial,helvetica">This article shows how to write CGI scripts, incorporate search engines, convert multiple text files to HTML, monitor log files, and track visitors to your site. This third and final installment looks at storing the data, the "visit" data structure, and the &store_line subroutine.</font>Syntax not understood
535 <p></p>Syntax not understood
536 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
537 <tr>Syntax not understood
538 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
539 <a href="/story/2001-12-11-002-06-OS-DT-MQ.html"><font size="4" face="arial,helvetica">Retro web application framework V1.1.0 release</font></a>Syntax not understood
540 </td>Syntax not understood
541 </tr>Syntax not understood
542 </table><font size="1">(Dec 11, 2001, 21:37 UTC) (4103 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
543 <font size="+0" face="arial,helvetica">Retro uses Apache and the mod_fastcgi module to provide the same kind of web application development facilities as jsp/servlet environments, and the IIS ASP environment.</font>Syntax not understood
544 <p></p>Syntax not understood
545 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
546 <tr>Syntax not understood
547 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
548 <a href="/story/2001-12-11-001-06-PR-BZ-SW.html"><font size="4" face="arial,helvetica">Leveraging open standards such as Java, JSP, XML,J2EE, Expresso and Struts.</font></a>Syntax not understood
549 </td>Syntax not understood
550 </tr>Syntax not understood
551 </table><font size="1">(Dec 11, 2001, 21:35 UTC) (6315 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
552 <font size="+0" face="arial,helvetica">"Now based on both Expresso and Apache Jakarta Struts, this move makes Jcorporate the first and only vendor in its marketplace to be based on the two dominant OSS Java Web application development frameworks in use today, a shared standard jointly comprising an estimated 850f that market."</font>Syntax not understood
553 <p></p>Syntax not understood
554 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
555 <tr>Syntax not understood
556 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
557 <a href="/story/2001-12-04-002-06-NW-CY.html"><font size="4" face="arial,helvetica">Netcraft Web Server Survey for November is available</font></a>Syntax not understood
558 </td>Syntax not understood
559 </tr>Syntax not understood
560 </table><font size="1">(Dec 4, 2001, 17:59 UTC) (7737 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
561 <font size="+0" face="arial,helvetica">Apache continues to be the top used web server with 56.81 percent.</font>Syntax not understood
562 <p></p>Syntax not understood
563 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
564 <tr>Syntax not understood
565 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
566 <a href="/story/2001-12-04-001-06-NW-SW-DT.html"><font size="4" face="arial,helvetica">FoxServ 2.0 Released</font></a>Syntax not understood
567 </td>Syntax not understood
568 </tr>Syntax not understood
569 </table><font size="1">(Dec 4, 2001, 17:53 UTC) (5654 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
570 <font size="+0" face="arial,helvetica">After intensive beta stage testing and some feedback, we are proud to present FoxServ 2.0. This version has changed a lot since beta 3. It has fixed the configurator issue on php and added MySQL frontend and Python 2.1.</font>Syntax not understood
571 <p></p>Syntax not understood
572 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
573 <tr>Syntax not understood
574 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
575 <a href="/story/2001-11-30-002-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Ace's Hardware: Building a Better Webserver in the 21st Century</font></a>Unknown directive
576 </td>Syntax not understood
577 </tr>Syntax not understood
578 </table><font size="1">(Nov 30, 2001, 20:12 UTC) (6880 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
579 <font size="+0" face="arial,helvetica">"Our old web application was written in PHP and ran on Apache, a "pre-fork" multiprocess HTTP server. Apache works by starting a parent process which then forks several child processes to listen and wait for HTTP connections. Since, each of these child processes serves one HTTP request at a time, Apache creates a pool of processes to handle connections in a timely fashion." This article talks about the hardware and software changes when upgrading a webserver. They end up using an alternative to Apache.</font>Syntax not understood
580 <p></p>Syntax not understood
581 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
582 <tr>Syntax not understood
583 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
584 <a href="/story/2001-11-30-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Web Techniques: Customer Number One</font></a>Unknown directive
585 </td>Syntax not understood
586 </tr>Syntax not understood
587 </table><font size="1">(Nov 30, 2001, 19:54 UTC) (4705 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
588 <font size="+0" face="arial,helvetica">"Whether you're administering a single, dedicated Web server, or one serving hundreds of hosts, each site's client expects and deserves a certain level of support and service. ..." This article covers mod_throttle, having each site operate under its own user ID, and running several instances of Apache.</font>Syntax not understood
589 <p></p>Syntax not understood
590 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
591 <tr>Syntax not understood
592 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
593 <a href="/story/2001-11-27-002-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Apache-Frontpage RPM project updated</font></a>Syntax not understood
594 </td>Syntax not understood
595 </tr>Syntax not understood
596 </table><font size="1">(Nov 27, 2001, 21:57 UTC) (7196 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
597 <font size="+0" face="arial,helvetica">This project makes it easier for new people to get FrontPage 2002 extensions running with Apache. It is now updated to use Apache 1.3.22.</font>Syntax not understood
598 <p></p>Syntax not understood
599 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
600 <tr>Syntax not understood
601 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
602 <a href="/story/2001-11-27-001-06-PS-CY.html"><font size="4" face="arial,helvetica">CNet: Open-source approach fades in tough times</font></a>Unknown directive
603 </td>Syntax not understood
604 </tr>Syntax not understood
605 </table><font size="1">(Nov 27, 2001, 20:15 UTC) (2682 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
606 <font size="+0" face="arial,helvetica">"On the business end, companies typically seek customers with the free software and derive revenue by selling services and support. ... But that's proved easier said than done."</font>Syntax not understood
607 <p></p>Syntax not understood
608 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
609 <tr>Syntax not understood
610 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
611 <a href="/story/2001-11-16-002-06-PS-BZ.html"><font size="4" face="arial,helvetica">NewsForge: VA spin-off releases first product, aims for profit</font></a>Unknown directive
612 </td>Syntax not understood
613 </tr>Syntax not understood
614 </table><font size="1">(Nov 16, 2001, 20:19 UTC) (3036 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
615 <font size="+0" face="arial,helvetica">"XAO Inc., a privately held spin off of VA Linux, announced the release of the XAO 1.0 Web server, a Web-services software package based on Apache."</font>Syntax not understood
616 <p></p>Syntax not understood
617 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
618 <tr>Syntax not understood
619 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
620 <a href="/story/2001-11-16-001-06-NW-CY-DP.html"><font size="4" face="arial,helvetica">Apache 2.0.28 Released as Beta</font></a>Syntax not understood
621 </td>Syntax not understood
622 </tr>Syntax not understood
623 </table><font size="1">(Nov 16, 2001, 19:05 UTC) (5696 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
624 <font size="+0" face="arial,helvetica">"The Apache Group is proud to announce the twenty-eighth release of Apache 2.0. This is the second public beta of Apache 2.0. This release has been tested thoroughly and has been running the apache.org web site since Nov. 9, 2001."</font>Syntax not understood
625 <p></p>Syntax not understood
626 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
627 <tr>Syntax not understood
628 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
629 <a href="/story/2001-11-12-001-06-PR-BZ-CY.html"><font size="4" face="arial,helvetica">Covalent Technologies announces industry support for Enterprise Ready Server and Apache 2.0</font></a>Syntax not understood
630 </td>Syntax not understood
631 </tr>Syntax not understood
632 </table><font size="1">(Nov 12, 2001, 20:52 UTC) (3726 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
633 <font size="+0" face="arial,helvetica">"In conjunction with the launch of Enterprise Ready Server, Covalent Technologies today announced a coalition of support for its new enterprise solution for the Apache Web server. A wide range of companies support the new software product designed to enhance the reliability, security and manageability of the world's most widely used Web server."</font>Syntax not understood
634 <p></p>Syntax not understood
635 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
636 <tr>Syntax not understood
637 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
638 <a href="/story/2001-11-07-001-06-PS-PH-AD.html"><font size="4" face="arial,helvetica">developer.com: On the Security of PHP, Part 1</font></a>Unknown directive
639 </td>Syntax not understood
640 </tr>Syntax not understood
641 </table><font size="1">(Nov 7, 2001, 13:56 UTC) (4914 reads) (3 talkbacks) (Posted by )</font><br>Unknown directive
642 <font size="+0" face="arial,helvetica">Despite the fact that PHP is designed with security in mind, a familiarity with its more dangerous aspects and conformance to common secure programming guidelines is essential to minimizing the possibility of security compromises. The aim of this document is to provide an overview of various security issues with PHP and to offer advice on secure PHP programming practices.</font>Syntax not understood
643 <p></p>Syntax not understood
644 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
645 <tr>Syntax not understood
646 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
647 <a href="/story/2001-11-06-001-06-PR-DP-MQ.html"><font size="4" face="arial,helvetica">Apache/PHP-based Content Management System Release</font></a>Syntax not understood
648 </td>Syntax not understood
649 </tr>Syntax not understood
650 </table><font size="1">(Nov 6, 2001, 12:33 UTC) (8741 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
651 <font size="+0" face="arial,helvetica">Digital Spinner, a web design and applications development company, announced today the fifth release candidate<br>Syntax not understood
652 of the GroupIT Engine, a PHP-based content management and group collaboration system capable of powering the next generation of web sites, intranets and extranets.</font>Syntax not understood
653 <p></p>Syntax not understood
654 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
655 <tr>Syntax not understood
656 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
657 <a href="/story/2001-11-05-001-06-PR-BZ-AD.html"><font size="4" face="arial,helvetica">HyperSpace Communications announces limited release of HyperSpace Accelerator software</font></a>Syntax not understood
658 </td>Syntax not understood
659 </tr>Syntax not understood
660 </table><font size="1">(Nov 5, 2001, 17:42 UTC) (3675 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
661 <font size="+0" face="arial,helvetica">"HyperSpace enables content providers to dramatically accelerate the transmission and receipt of data over the Internet through a sharp reduction in bandwidth requirement. ... HyperSpace is the full-featured, commercial version of what began as Mod_gzip, a free, downloadable module the Company began offering a year ago to users of Apache servers."</font>Syntax not understood
662 <p></p>Syntax not understood
663 <center>Syntax not understood
664 <a name="normalnews" id="normalnews">&nbsp;</a><a href="/preferences.php3?area=topiclow">-= Filtered [less interesting] news below =-</a>Syntax not understood
665 </center>Syntax not understood
666 <p></p>Syntax not understood
667 <center>Syntax not understood
668 <a name="boringnews" id="boringnews">&nbsp;</a><a href="/preferences.php3?area=topichigh">-= Highlighted=0 Regular=40 Boring=0 =-<br>Syntax not understood
669 -= Click here to change filter settings =-</a>Syntax not understood
670 </center>Syntax not understood
671 <p></p>Syntax not understood
672 </td>Syntax not understood
673 <td width="20%" valign="top" align="right">Syntax not understood
674 <table border="0" width="100%">Syntax not understood
675 <tr>Syntax not understood
676 <td>Syntax not understood
677 <form method="post" action="/account.php3">Syntax not understood
678 <table align="center" border="0">Syntax not understood
679 <tr>Syntax not understood
680 <td colspan="2"><font size="-1">Your Apache Today<br>Syntax not understood
681 <a href="/about.php3#YLT"><b>Find Out Why!</b></a></font></td>Syntax not understood
682 </tr>Syntax not understood
683 <tr>Syntax not understood
684 <td><font size="-1">Login</font></td>Syntax not understood
685 <td><input type="text" size="8" name="username"></td>Syntax not understood
686 </tr>Syntax not understood
687 <tr>Syntax not understood
688 <td><font size="-1">Password</font></td>Syntax not understood
689 <td><input type="password" size="8" name="passwd"></td>Syntax not understood
690 </tr>Syntax not understood
691 <tr>Syntax not understood
692 <td><input type="submit" name="login" value="Login"></td>Syntax not understood
693 <td><input type="submit" name="create" value="Create"> <input type="hidden" name="redirect" value=""> <input type="hidden" name="loginboxtag" value="loginbox"></td>Syntax not understood
694 </tr>Syntax not understood
695 </table>Syntax not understood
696 </form>Syntax not understood
697 </td>Syntax not understood
698 </tr>Syntax not understood
699 </table>Syntax not understood
700 <p></p>Syntax not understood
701 <center>Syntax not understood
702 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/1423649654/125x125-1/House_ISP_Expo_3x/ispbusexpo_125_new.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/House_ISP_Expo_3x/ispbusexpo_125_new.gif" width="125" height="125" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/1423649654/125x125-1/House_ISP_Expo_3x/ispbusexpo_125_new.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
703 </center>Syntax not understood
704 <p></p>Syntax not understood
705 <div align="left">Syntax not understood
706 <font size="+1" face="arial,helvetica"><b>Latest Feature</b></font>Syntax not understood
707 <p></p>Syntax not understood
708 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
709 <tr>Syntax not understood
710 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
711 <a href="https://www.ssl.org"><font size="3" face="arial,helvetica">SSL checker</font></a>Unknown directive
712 </td>Syntax not understood
713 </tr>Syntax not understood
714 </table>Apache mod_ssl is a web server module that helps in providing secure communication via TLS protocols. Verify TLS/SSL certificate installation errors.<br>Syntax not understood
715 (August 12, 2024) <p></p>Syntax not understood
716 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
717 <tr>Syntax not understood
718 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
719 <a href="/news_story.php3?ltsn=2000-06-30-002-01-NW-LF-SW"><font size="3" face="arial,helvetica">Looking at Apache 2.0 Alpha 4</font></a>Syntax not understood
720 </td>Syntax not understood
721 </tr>Syntax not understood
722 </table>Development continues to roll along on Apache 2.0. In his latest column, Ryan Bloom details what's new in the recently released Apache 2.0 Alpha 4.<br>Syntax not understood
723 (Jun 30, 2000)Syntax not understood
724 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
725 <tr>Syntax not understood
726 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
727 </tr>Syntax not understood
728 </table><font size="+1" face="arial,helvetica"><b>Apache Today Features</b></font>Syntax not understood
729 <p></p>Syntax not understood
730 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
731 <tr>Syntax not understood
732 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
733 <a href="/news_story.php3?ltsn=2000-09-27-001-01-OP-CY-LF"><font size="3" face="arial,helvetica">The Apache Web Server Documentation Project</font></a>Syntax not understood
734 </td>Syntax not understood
735 </tr>Syntax not understood
736 </table>Over the years, a lot of people have become interested in the idea of contributing to the Apache HTTP Server project, but have hung back or remained silent because they felt only hardcore C programmers with tons of experience need apply. Some actually have contacted the Project, saying they'd like to help out but don't have the coding skills and so didn't know what they could do. And some have offered specifically to help out on the documentation, either translating it, or correcting technical nits, or improving its readability or navigability. In July of 2000, however, the Apache HTTP server project created a subproject and reorganised the documentation files so that they can be worked on directly by non-programmers. This article describes more about this, and how you can get involved.<br>Syntax not understood
737 (Sep 27, 2000)Syntax not understood
738 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
739 <tr>Syntax not understood
740 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
741 </tr>Syntax not understood
742 </table>Syntax not understood
743 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
744 <tr>Syntax not understood
745 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
746 <a href="/news_story.php3?ltsn=2000-06-14-002-01-PS"><font size="3" face="arial,helvetica">Keeping Your Images from Adorning Other Sites</font></a>Syntax not understood
747 </td>Syntax not understood
748 </tr>Syntax not understood
749 </table>Webmasters are ever searching for ways to make their sites look cool and attractive. One way is to dress it up with images, logos, and other graphics--sometimes referred to as 'eye candy.' Of course, if you happen to be in the forefront of this in any way, you run the risk of having others cadge <i>your</i> art in order to dress up <i>their</i> sites. This article shows how you can use Apache configuration directives to limit access to your art so that it's more difficult to use elsewhere.<br>Syntax not understood
750 (Jun 14, 2000)Syntax not understood
751 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
752 <tr>Syntax not understood
753 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
754 </tr>Syntax not understood
755 </table>Syntax not understood
756 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
757 <tr>Syntax not understood
758 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
759 <a href="/news_story.php3?ltsn=2000-05-31-001-08-NW-LF"><font size="3" face="arial,helvetica">E-Commerce Solutions: An Apache Overview</font></a>Unknown directive
760 </td>Syntax not understood
761 </tr>Syntax not understood
762 </table>With this column Martin C. Brown begin his regular coverage of Apache and E-Commerce for Apache Today. This initial column maps out the burgeoning area of E-Commerce and what every Apache Webmaster needs to know about implementing E-Commerce on their site.<br>Syntax not understood
763 (May 31, 2000)Syntax not understood
764 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
765 <tr>Syntax not understood
766 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
767 </tr>Syntax not understood
768 </table>Syntax not understood
769 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
770 <tr>Syntax not understood
771 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
772 <a href="/news_story.php3?ltsn=2000-05-28-004-01-PS"><font size="3" face="arial,helvetica">An Introduction to Apache 2.0</font></a>Syntax not understood
773 </td>Syntax not understood
774 </tr>Syntax not understood
775 </table>Apache 2.0 has already been through three alpha releases. In this preview, Ryan Bloom of the Apache Group previews Apache 2.0 and explains why it will make life easier for every Webmaster on the Internet.<br>Syntax not understood
776 (May 28, 2000)Syntax not understood
777 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
778 <tr>Syntax not understood
779 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
780 </tr>Syntax not understood
781 </table>Syntax not understood
782 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
783 <tr>Syntax not understood
784 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
785 <a href="/news_story.php3?ltsn=2000-06-1-001-01-NW-DP-LF"><font size="3" face="arial,helvetica">Getting Started with Apache 1.3</font></a>Syntax not understood
786 </td>Syntax not understood
787 </tr>Syntax not understood
788 </table>While you're licking your chops and waiting for Apache 2.0 to be released, you're probably facing a very real situation of having to set up an Apache Web server today. In this overview, Apache pioneer Ken Coar goes through all the steps needed to install and configure an Apache 1.3 Web server.<br>Syntax not understood
789 (Jun 1, 2000)Syntax not understood
790 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
791 <tr>Syntax not understood
792 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
793 </tr>Syntax not understood
794 </table>Syntax not understood
795 </div>Syntax not understood
796 <p></p>Syntax not understood
797 <div align="left"></div>Syntax not understood
798 <div align="left">Syntax not understood
799 <p></p>Syntax not understood
800 <table cellspacing="1" cellpadding="4" border="0" width="100%">Syntax not understood
801 <tr>Syntax not understood
802 <td valign="middle" align="center"><b>www.BSDtoday.com</b></td>Syntax not understood
803 </tr>Syntax not understood
804 <tr>Syntax not understood
805 <td>"Linux Journal: Why I Don't Use the GPL<br>Unknown directive
806 ""It has Excel and Word"<br>Syntax not understood
807 "ZDNet: Want a Windows alternative? Try BSD<br>Unknown directive
808 "Changes to the NetBSD Packages Collection in February 2002<br>Syntax not understood
809 "Linux and main: Running a corporation in an open source world<br>Unknown directive
810 "Linux Journal: Hardening Sendmail<br>Unknown directive
811 "OSNews: Understanding CVSup, Mounting, Ports and Init on FreeBSD<br>Unknown directive
812 "ONLamp: BSDCon 2002<br>Unknown directive
813 "Wind River announces product rollout plans for future BSD/OS releases<br>Syntax not understood
814 "Wind River announces BSD/OS 4.3 release<br></td>Syntax not understood
815 </tr>Syntax not understood
816 </table>Syntax not understood
817 <p></p>Syntax not understood
818 <table cellspacing="1" cellpadding="4" border="0" width="100%">Syntax not understood
819 <tr>Syntax not understood
820 <td valign="middle" align="center"><b>PHPBuilder.com New Articles</b></td>Syntax not understood
821 </tr>Syntax not understood
822 <tr>Syntax not understood
823 <td>"Getting started with php and InterBase<br>Syntax not understood
824 "Configuring PHP with ORACLE 8i Support<br>Syntax not understood
825 "Using PHP and MySQL with Flash<br>Syntax not understood
826 "Making PHP Applications Cache-Friendly<br>Syntax not understood
827 "Making forms object-oriented<br>Syntax not understood
828 "PHP programming methodologies and documentation<br>Syntax not understood
829 "Using Webalizer to analyze Apache logs<br>Syntax not understood
830 "Optimizing Postgresql<br>Syntax not understood
831 "Getting Started with PHP/Ming<br>Syntax not understood
832 "Cross-platform and Portable Development With PHP<br></td>Syntax not understood
833 </tr>Syntax not understood
834 </table>Syntax not understood
835 <p></p>Syntax not understood
836 <table cellspacing="1" cellpadding="4" border="0" width="100%">Syntax not understood
837 <tr>Syntax not understood
838 <td valign="middle" align="center"><b>Linux Today</b></td>Syntax not understood
839 </tr>Syntax not understood
840 <tr>Syntax not understood
841 <td>Syntax not understood
842 <center>Syntax not understood
843 <p><img src="http://linuxtoday.com/pics/ltnet.png" alt="Linux Today" border="0"></p>Unknown directive
844 </center>Syntax not understood
845 <p>"NewsForge: A Tale of Two Linux Bootable Business Cards<br>Unknown directive
846 "Java.Sun.com: Java Community Process Embraces Open Source<br>Unknown directive
847 "Computerworld New Zealand: Linux Wannabes Get Help<br>Unknown directive
848 "ZDNet UK: Stallman: Patents Victimize Developers<br>Unknown directive
849 "Linux Weekly News for March 28, 2002<br></p>Syntax not understood
850 <form method="get" action="http://linuxtoday.com/search.php3">Unknown directive
851 Search Linux Today:<br>Unknown directive
852 <input type="text" name="query"><br>Syntax not understood
853 <input type="submit" value="Search">Syntax not understood
854 </form>Syntax not understood
855 </td>Syntax not understood
856 </tr>Syntax not understood
857 </table><font size="-1"></font>Syntax not understood
858 <center>Syntax not understood
859 <a href="/preferences.php3?area=upflag2"><font size="-1">Content settings.</font></a>Syntax not understood
860 </center>Syntax not understood
861 </div>Syntax not understood
862 </td>Syntax not understood
863 </tr>Syntax not understood
864 </table>Syntax not understood
865 <table align="center" border="0" cellpadding="10" cellspacing="0">Syntax not understood
866 <tr>Syntax not understood
867 <td align="center">Syntax not understood
868 <img height="17" width="120" src="/pics/icom-micros.png" border="0" alt="To internet.com">Syntax not understood
869 <p></p>Syntax not understood
870 </td>Syntax not understood
871 </tr>Syntax not understood
872 <tr>Syntax not understood
873 <td>Syntax not understood
874 <center>Syntax not understood
875 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/934345979/468x60-2/Covalent_Technologies_4b/new_ERS_seminar_750x100.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/Covalent_Technologies_4b/new_ERS_seminar_750x100.gif" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/934345979/468x60-2/Covalent_Technologies_4b/new_ERS_seminar_750x100.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
876 </center>Syntax not understood
877 </td>Syntax not understood
878 </tr>Syntax not understood
879 </table>Syntax not understood
880 <center>Syntax not understood
881 <script language="javascript" src="http://ss.webring.yahoo.com/navbar?f=j&y=paulmferris&u=97084277210026050"></script>Unknown directive
882 </center>Syntax not understood
883 <table bgcolor="#0044DE" width="100%">Syntax not understood
884 <tr align="center">Syntax not understood
885 <td bgcolor="#FF3300">Syntax not understood
886 <a href="/triggerFAQ.php3"><font color="#FFFFFF"><b>About Triggers</b></font></a>Syntax not understood
887 </td>Syntax not understood
888 <td bgcolor="#DD7400">Syntax not understood
889 <a href="/mediakit.php3"><font color="#FFFFFF"><b>Media Kit</b></font></a>Syntax not understood
890 </td>Syntax not understood
891 <td bgcolor="#999900">Syntax not understood
892 <a href="/index.php3?override=64"><font color="#FFFFFF"><b>Security</b></font></a>Syntax not understood
893 </td>Syntax not understood
894 <td bgcolor="#00BB44">Syntax not understood
895 <a href="/trigger.php3"><font color="#FFFFFF"><b>Triggers</b></font></a>Syntax not understood
896 </td>Syntax not understood
897 <td bgcolor="#009999">Syntax not understood
898 <a href="/account.php3"><font color="#FFFFFF"><b>Login</b></font></a>Syntax not understood
899 </td>Syntax not understood
900 </tr>Syntax not understood
901 </table>Syntax not understood
902 <p></p>Syntax not understood
903 <table border="0" cellpadding="3" cellspacing="0" bgcolor="#FFFFFF" width="100%">Syntax not understood
904 <tr>Syntax not understood
905 <td align="center">Syntax not understood
906 <font size="2" face="Arial, Helvetica, sans-serif"><br>Syntax not understood
907 All times are recorded in UTC.<br>Syntax not understood
908 Linux is a trademark of Linus Torvalds.<br>Syntax not understood
909 Powered by Linux 2.4, Apache 1.3, and PHP 4</font>Syntax not understood
910 <center>Syntax not understood
911 <font size="2" face="Arial, Helvetica, sans-serif"><span class="foot">Copyright 2002 INT Media Group, Incorporated All Rights Reserved.</span><br>Syntax not understood
912 Legal Notices, �Licensing, Reprints, & Permissions, �Privacy Policy.<br>Syntax not understood
913 <img src="/img/URL.gif" alt="http://www.internet.com/" width="161" height="18" border="0"></font>Unknown directive
914 </center><font size="2" face="Arial, Helvetica, sans-serif"></font>Syntax not understood
915 </td>Syntax not understood
916 </tr>Syntax not understood
917 </table>Syntax not understood
918 </center>Syntax not understood
919 </center>Syntax not understood
920</body>Syntax not understood
921</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
36
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
69
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

834 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

874 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

871 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

874 ms

Detailed Report

Audit breakdown by category with detailed findings.

99

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB
apachetoday.com/0.0 ms60.0 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
body > center > a > img body > center > a > img
/RealMedia/ads/Creatives/Covalent_Technologies_4a/new_ERS...
Be proactive with SiteScope. FREE trial today. tr > td > a > img
apachetoday.com/RealMedia/ads/Creatives/Mercury_Interactive_2b/SSeyes125x800.gif
td > center > a > img td > center > a > img
/RealMedia/ads/Creatives/Covalent_Technologies_4b/new_ERS...
Linux Today td > center > p > img
linuxtoday.com/pics/ltnet.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Time to Interactive 0.9 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 333 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.1 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 160 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 310 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
Avoid large layout shifts
36

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Breaking News td > a > font > b
Preferences td > a > font > b
Contribute td > a > font > b
About td > a > font > b
Apache Module Registry tr > td > font > b
ApacheCon tr > td > font > b
Apache-Perl Integration Project tr > td > font > b
The Java Apache Project tr > td > font > b
PHP Server Side Scripting tr > td > font > b
The Apache FAQ tr > td > font > b
Apache Project tr > td > font > b
The Jakarta Project tr > td > font > b
About Triggers td > a > font > b
Media Kit td > a > font > b
Security td > a > font > b
Triggers td > a > font > b
Login td > a > font > b

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > center > img body > center > img
tbody > tr > td > img tbody > tr > td > img
tbody > tr > td > img tbody > tr > td > img
tr > td > center > img tr > td > center > img
tr > td > center > img tr > td > center > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
td > form > font > input td > form > font > input
td > form > font > input td > form > font > input
form > p > font > input form > p > font > input
tbody > tr > td > input tbody > tr > td > input
tbody > tr > td > input tbody > tr > td > input
tr > td > form > input tr > td > form > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Right Now Yesterday 2 Days Ago 3 Days Ago 4 Days Ago 5 Days Ago 6 Days Ago 1 We… tr > td > font > select#LTTimeframe
Date Reverse Date Reads Reverse Reads Talkback Rev. Talkback tr > td > font > select#LTSortOpt

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > center > a body > center > a
tbody > tr > td > a tbody > tr > td > a
tr > td > center > a tr > td > center > a
tr > td > center > a tr > td > center > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Be proactive with SiteScope. FREE trial today. tbody > tr > td > a
form > p > font > input form > p > font > input
Date Reverse Date Reads Reverse Reads Talkback Rev. Talkback tr > td > font > select#LTSortOpt
-= Highlighted stories above -- Normal news below =- tr > td > center > a
tr > td > form > input tr > td > form > input

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Planet Linux Today Linux Central PHPBuilder Linux Apps Apache Today Just … tbody > tr > td > table
Apache Module Registry ApacheCon Apache-Perl Integration Project The Java Apach… tbody > tr > td > table

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Planet Linux Today Linux Central PHPBuilder Linux Apps Apache Today Just … tbody > tr > td > table
Apache Module Registry ApacheCon Apache-Perl Integration Project The Java Apach… tbody > tr > td > table
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Input buttons have discernible text.
Document has a `<title>` element
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
69

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
ss.webring.yahoo.com/navbar?f=j&y=paulmferris&u=97084277210026050Blocked
linuxtoday.com/pics/ltnet.pngAutomatically upgraded to HTTPS
linuxcentral.com/cgi-bin/sredAllowed with warning
e-newsletters.internet.com/cgi-bin/subscribeAllowed with warning
linuxtoday.com/search.php3Allowed with warning

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
tr > td > a > img tr > td > a > img
apachetoday.com/RealMedia/ads/Creatives/default/empty.gif2 x 21 x 12 x 2

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Mixed Content: The page at 'https://apachetoday.com/' was loaded over HTTPS, but requested an insecure script 'http://ss.webring.yahoo.com/navbar?f=j&y=paulmferris&u=97084277210026050'. This request has been blocked; the content must be served over HTTPS.
apachetoday.com/ line 13, col 113
ReferenceError: getCookie is not defined at onload (https://apachetoday.com/:14:114)

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Detected JavaScript libraries
75

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > center > img body > center > img
tbody > tr > td > img tbody > tr > td > img
tbody > tr > td > img tbody > tr > td > img
tr > td > center > img tr > td > center > img
tr > td > center > img tr > td > center > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html>Syntax not understood
3<head>Syntax not understood
4 <title>Apache Today - Apache News for 03/29/2002</title>Syntax not understood
5 <style>Syntax not understood
7 <!--Syntax not understood
8 TD.lcnormal {font-family:arial,helvetica,sans-serif;}Unknown directive
9 A.lcnormal {color:0066FF;}Unknown directive
10 A.lcnormal:hover {color:cc9900;}Unknown directive
11 // -->Syntax not understood
12 </style>Syntax not understood
13</head>Syntax not understood
14<body onload="getCookie('surveyflag')" bgcolor="#FFFFFF" link="#0044DE" text="#002244" vlink="black" alink="red">Syntax not understood
15 <center>Syntax not understood
16 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/877874199/468x60-1/Covalent_Technologies_4a/new_ERS_seminar_750x100.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/Covalent_Technologies_4a/new_ERS_seminar_750x100.gif" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/877874199/468x60-1/Covalent_Technologies_4a/new_ERS_seminar_750x100.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
17 <center>Syntax not understood
18 <table border="0" width="100%">Syntax not understood
19 <tr>Syntax not understood
20 <td align="left"><font size="-1">Your Daily Source for Apache News and Information</font></td>Syntax not understood
21 <td align="center">&nbsp;</td>Syntax not understood
22 <td align="right">Syntax not understood
23 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/1287080011/sitetext-1/default/empty.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/default/empty.gif" width="2" height="2" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/1287080011/sitetext-1/default/empty.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
24 </td>Syntax not understood
25 </tr>Syntax not understood
26 </table>Syntax not understood
27 <table bgcolor="#0044DE" width="100%">Syntax not understood
28 <tr align="center">Syntax not understood
29 <td bgcolor="#999900">Syntax not understood
30 <a href="/"><font color="#FFFFFF"><b>Breaking News</b></font></a>Syntax not understood
31 </td>Syntax not understood
32 <td bgcolor="#00BB44">Syntax not understood
33 <a href="/preferences.php3"><font color="#FFFFFF"><b>Preferences</b></font></a>Syntax not understood
34 </td>Syntax not understood
35 <td bgcolor="#009999">Syntax not understood
36 <a href="/contribute.php3"><font color="#FFFFFF"><b>Contribute</b></font></a>Syntax not understood
37 </td>Syntax not understood
38 <td bgcolor="#0044DD">Syntax not understood
39 <a href="/trigger.php3"><font color="#FFFFFF"><b>Triggers</b></font></a>Syntax not understood
40 </td>Syntax not understood
41 <td bgcolor="#3300FF">Syntax not understood
42 <a href="/linkus.php3"><font color="#FFFFFF"><b>Link Us</b></font></a>Syntax not understood
43 </td>Syntax not understood
44 <td bgcolor="#9900FF">Syntax not understood
45 <a href="/search.php3"><font color="#FFFFFF"><b>Search</b></font></a>Syntax not understood
46 </td>Syntax not understood
47 <td bgcolor="#FF0099">Syntax not understood
48 <a href="/about.php3"><font color="#FFFFFF"><b>About</b></font></a>Syntax not understood
49 </td>Syntax not understood
50 </tr>Syntax not understood
51 </table>Syntax not understood
52 <p></p>Syntax not understood
53 <table border="0" width="100%" cellpadding="6" cellspacing="0">Syntax not understood
54 <tr>Syntax not understood
55 <td width="130" valign="top">Syntax not understood
56 <a href="/"><img height="60" width="160" src="/pics/at_logo.png" border="0" alt="Apache Today [Your Apache News Source]"></a> <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/923878324/125x800/Mercury_Interactive_2b/SSeyes125x800.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/Mercury_Interactive_2b/SSeyes125x800.gif" alt="Be proactive with SiteScope. FREE trial today." border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/923878324/125x800/Mercury_Interactive_2b/SSeyes125x800.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0"><br>Syntax not understood
57 <table border="0" cellpadding="0" cellspacing="4" width="120">Syntax not understood
58 <tr bgcolor="#FFFFFF">Syntax not understood
59 <td align="center">Syntax not understood
60 <img src="/pics/logo_osl_inetcom_wtux.png" width="117" height="57" border="0" alt="The Linux Channel at internet.com" vspace="3"><br>Syntax not understood
61 <table border="0" width="100%">Syntax not understood
62 <tr>Syntax not understood
63 <td colspan="3"><font size="-1">Linux&nbsp;Planet</font></td>Syntax not understood
64 </tr>Syntax not understood
65 <tr>Syntax not understood
66 <td colspan="3"><font size="-1">Linux&nbsp;Today</font></td>Syntax not understood
67 </tr>Syntax not understood
68 <tr>Syntax not understood
69 <td colspan="3"><font size="-1">Linux&nbsp;Central</font></td>Syntax not understood
70 </tr>Syntax not understood
71 <tr>Syntax not understood
72 <td colspan="3"><font size="-1">PHPBuilder</font></td>Syntax not understood
73 </tr>Syntax not understood
74 <tr>Syntax not understood
75 <td colspan="3"><font size="-1">Linux&nbsp;Apps</font></td>Syntax not understood
76 </tr>Syntax not understood
77 <tr>Syntax not understood
78 <td colspan="3">Syntax not understood
79 <a href="/"><font size="-1">Apache&nbsp;Today</font></a>Syntax not understood
80 </td>Syntax not understood
81 </tr>Syntax not understood
82 <tr>Syntax not understood
83 <td colspan="3"><font size="-1">Just&nbsp;Linux</font></td>Syntax not understood
84 </tr>Syntax not understood
85 <tr>Syntax not understood
86 <td colspan="3"><font size="-1">Linux&nbsp;Programming</font></td>Syntax not understood
87 </tr>Syntax not understood
88 <tr>Syntax not understood
89 <td colspan="3"><font size="-1">BSD&nbsp;Today</font></td>Syntax not understood
90 </tr>Syntax not understood
91 <tr>Syntax not understood
92 <td colspan="3"><font size="-1">All&nbsp;Linux Devices</font></td>Syntax not understood
93 </tr>Syntax not understood
94 <tr>Syntax not understood
95 <td colspan="3"><font size="-1">Enterprise Linux&nbsp;Today</font></td>Syntax not understood
96 </tr>Syntax not understood
97 <tr>Syntax not understood
98 <td colspan="3"><font size="-1">Linuxnewbie.org</font></td>Syntax not understood
99 </tr>Syntax not understood
100 <tr>Syntax not understood
101 <td colspan="3"><font size="-1">BSD&nbsp;Central</font></td>Syntax not understood
102 </tr>Syntax not understood
103 <tr>Syntax not understood
104 <td colspan="3"><font size="-1">Linux&nbsp;Start</font></td>Syntax not understood
105 </tr>Syntax not understood
106 <tr align="center" bgcolor="#0044DE">Syntax not understood
107 <td><font size="1"><font color="#FFFFFF">SITE DESCRIPTIONS</font></font></td>Syntax not understood
108 </tr>Syntax not understood
109 </table>Syntax not understood
110 </td>Syntax not understood
111 </tr>Syntax not understood
112 </table>Syntax not understood
113 <table cellspacing="0" cellpadding="0" width="130" border="0">Syntax not understood
114 <tr>Syntax not understood
115 <td bgcolor="#EEEEEE" height="2" colspan="2" width="130">Syntax not understood
116 <hr noshade>Syntax not understood
117 </td>Syntax not understood
118 </tr>Syntax not understood
119 <tr>Syntax not understood
120 <td bgcolor="#EEEEEE" width="5">&nbsp;</td>Syntax not understood
121 <td bgcolor="#EEEEEE"><font color="#333333" size="-1"><b>internet.com</b></font><br>Syntax not understood
122 <font color="#333333" size="-1"><br>Syntax not understood
123 Internet News<br>Syntax not understood
124 Internet Investing<br>Syntax not understood
125 Internet Technology<br>Syntax not understood
126 Windows Internet Tech.<br>Syntax not understood
127 Linux/Open Source<br>Syntax not understood
128 Web Developer<br>Syntax not understood
129 ECommerce/Marketing<br>Syntax not understood
130 ISP Resources<br>Syntax not understood
131 ASP Resources<br>Syntax not understood
132 Wireless Internet<br>Syntax not understood
133 Downloads<br>Syntax not understood
134 Internet Resources<br>Syntax not understood
135 Internet Lists<br>Syntax not understood
136 International<br>Syntax not understood
137 EarthWeb<br>Syntax not understood
138 Career Resources<br>Syntax not understood
139 <br>Syntax not understood
140 Search internet.com<br>Syntax not understood
141 Advertising Info<br>Syntax not understood
142 Corporate Info<br></font></td>Syntax not understood
143 </tr>Syntax not understood
144 </table>Syntax not understood
145 <p></p>Syntax not understood
146 <table border="0" cellpadding="0" cellspacing="0" width="130">Syntax not understood
147 <tr bgcolor="#FFFFFF">Syntax not understood
148 <td align="center">Syntax not understood
149 <img src="/pics/logo_feather.png" width="119" height="34" border="0" alt="Apache HTTPD Links" vspace="0"><br>Syntax not understood
150 <table border="0" cellpadding="0" cellspacing="0" width="100%">Syntax not understood
151 <tr>Syntax not understood
152 <td colspan="3"><font size="-1" color="#FF0022"><b>Apache Module Registry</b></font></td>Syntax not understood
153 </tr>Syntax not understood
154 <tr>Syntax not understood
155 <td colspan="3"><font size="-1" color="#FF3300"><b>ApacheCon</b></font></td>Syntax not understood
156 </tr>Syntax not understood
157 <tr>Syntax not understood
158 <td colspan="3"><font size="-1" color="#DD7400"><b>Apache-Perl Integration Project</b></font></td>Syntax not understood
159 </tr>Syntax not understood
160 <tr>Syntax not understood
161 <td colspan="3"><font size="-1" color="#999900"><b>The Java Apache Project</b></font></td>Syntax not understood
162 </tr>Syntax not understood
163 <tr>Syntax not understood
164 <td colspan="3"><font size="-1" color="#00BB44"><b>PHP Server Side Scripting</b></font></td>Syntax not understood
165 </tr>Syntax not understood
166 <tr>Syntax not understood
167 <td colspan="3"><font size="-1" color="#009999"><b>The Apache FAQ</b></font></td>Syntax not understood
168 </tr>Syntax not understood
169 <tr>Syntax not understood
170 <td colspan="3"><font size="-1" color="#0044DD"><b>Apache XML Project</b></font></td>Syntax not understood
171 </tr>Syntax not understood
172 <tr>Syntax not understood
173 <td colspan="3"><font size="-1" color="#3300FF"><b>Apache-Related Projects</b></font></td>Syntax not understood
174 </tr>Syntax not understood
175 <tr>Syntax not understood
176 <td colspan="3"><font size="-1" color="#9900FF"><b>The Apache Software Foundation</b></font></td>Syntax not understood
177 </tr>Syntax not understood
178 <tr>Syntax not understood
179 <td colspan="3"><font size="-1" color="#FF0099"><b>Apache Project</b></font></td>Syntax not understood
180 </tr>Syntax not understood
181 <tr>Syntax not understood
182 <td colspan="3"><font size="-1" color="#FF0022"><b>The Jakarta Project</b></font></td>Syntax not understood
183 </tr>Syntax not understood
184 </table>Syntax not understood
185 </td>Syntax not understood
186 </tr>Syntax not understood
187 </table>Syntax not understood
188 <p></p>Syntax not understood
189 <table bgcolor="#000000" border="0" width="140">Syntax not understood
190 <tr>Syntax not understood
191 <td>Syntax not understood
192 <table cellspacing="1" cellpadding="4" bgcolor="#FFFFFF" border="0" width="100%">Syntax not understood
193 <tr>Syntax not understood
194 <td valign="middle" align="center" bgcolor="#EEEEEE"><font color="#000000" face="arial,helvetica,sans-serif"><b>linuxcentral.com: New Products</b></font></td>Syntax not understood
195 </tr>Syntax not understood
196 <tr>Syntax not understood
197 <td>Syntax not understood
198 <center>Syntax not understood
199 <p><img src="/pics/lc_logo130.png" alt="linuxcentral.com" border="0" width="130" height="44"></p>Syntax not understood
200 </center>Syntax not understood
201 <p>"<font face="arial,helvetica,sans-serif">Mandrake Linux ProSuite Edition 8.2 (PRE-ORDER)</font><br>Syntax not understood
202 "<font face="arial,helvetica,sans-serif">Mandrake Linux PowerPack Edition 8.2 (PRE-ORDER)</font><br>Syntax not understood
203 "<font face="arial,helvetica,sans-serif">Linux Administration: A Beginner's Guide</font><br>Unknown directive
204 "<font face="arial,helvetica,sans-serif">BRU Pro 2.0</font><br>Syntax not understood
205 "<font face="arial,helvetica,sans-serif">Building Linux Virtual Private Networks (VPNs)</font><br>Syntax not understood
206 "<font face="arial,helvetica,sans-serif">Linux Routing</font><br>Syntax not understood
207 "<font face="arial,helvetica,sans-serif">Mandrake Linux 8.2 (3 CD set) PRE-ORDER</font><br>Syntax not understood
208 "<font face="arial,helvetica,sans-serif">The Book of VMware</font><br>Syntax not understood
209 "<font face="arial,helvetica,sans-serif">Quanta Gold</font><br>Syntax not understood
210 "<font face="arial,helvetica,sans-serif">Rekall</font><br></p>Syntax not understood
211 <form method="get" action="http://linuxcentral.com/cgi-bin/sred">Unknown directive
212 <font size="2" face="arial,helvetica,sans-serif"><b>Search for Linux products</b><br>Syntax not understood
213 <input type="text" name="s_prod_name" size="15"><br></font>Syntax not understood
214 </form>Syntax not understood
215 </td>Syntax not understood
216 </tr>Syntax not understood
217 </table>Syntax not understood
218 </td>Syntax not understood
219 </tr>Syntax not understood
220 </table>Syntax not understood
221 <p></p>Syntax not understood
222 <center>Syntax not understood
223 Serverwatch<br>Syntax not understood
224 NewsletterSyntax not understood
225 </center>Syntax not understood
226 <table align="center" border="0">Syntax not understood
227 <tr>Syntax not understood
228 <td>Syntax not understood
229 <font size="-1"></font>Syntax not understood
230 <form action="http://e-newsletters.internet.com/cgi-bin/subscribe" method="post">Unknown directive
231 <font size="-1"><br>Syntax not understood
232 <input type="checkbox" name="List_Name" value="serverwatch-text"> Subscribe News<br></font>Syntax not understood
233 <p><font size="-1"><input type="text" name="email" size="20" value="enter email"> <input type="submit" name="Submit" value="Submit"></font></p>Syntax not understood
234 </form>Syntax not understood
235 </td>Syntax not understood
236 </tr>Syntax not understood
237 </table>Syntax not understood
238 </td>Syntax not understood
239 <td valign="top">Syntax not understood
240 <form name="TIMEFRAME" action="/index.php3" method="get" id="TIMEFRAME">Syntax not understood
241 <table width="99%" border="0" cellspacing="0" cellpadding="0">Syntax not understood
242 <tr valign="middle" align="center">Syntax not understood
243 <td>Time Frame</td>Syntax not understood
244 <td>Sort Order</td>Syntax not understood
245 <td>View</td>Syntax not understood
246 </tr>Syntax not understood
247 <tr valign="middle" align="center">Syntax not understood
248 <td><font size="-2"><select id="LTTimeframe" name="LTD">Syntax not understood
249 <option value="Now" selected>Syntax not understood
250 Right NowSyntax not understood
251 </option>Syntax not understood
252 <option value="Day-1">Syntax not understood
253 YesterdaySyntax not understood
254 </option>Syntax not understood
255 <option value="Day-2">Syntax not understood
256 2 Days AgoSyntax not understood
257 </option>Syntax not understood
258 <option value="Day-3">Syntax not understood
259 3 Days AgoSyntax not understood
260 </option>Syntax not understood
261 <option value="Day-4">Syntax not understood
262 4 Days AgoSyntax not understood
263 </option>Syntax not understood
264 <option value="Day-5">Syntax not understood
265 5 Days AgoSyntax not understood
266 </option>Syntax not understood
267 <option value="Day-6">Syntax not understood
268 6 Days AgoSyntax not understood
269 </option>Syntax not understood
270 <option value="Day-7">Syntax not understood
271 1 Week AgoSyntax not understood
272 </option>Syntax not understood
273 </select></font></td>Syntax not understood
274 <td><font size="-2"><select id="LTSortOpt" name="LTS">Syntax not understood
275 <option value="Ftimestamp">Syntax not understood
276 DateSyntax not understood
277 </option>Syntax not understood
278 <option value="Rtimestamp">Syntax not understood
279 Reverse DateSyntax not understood
280 </option>Syntax not understood
281 <option value="Freads">Syntax not understood
282 ReadsSyntax not understood
283 </option>Syntax not understood
284 <option value="Rreads">Syntax not understood
285 Reverse ReadsSyntax not understood
286 </option>Syntax not understood
287 <option value="Ftalkback">Syntax not understood
288 TalkbackSyntax not understood
289 </option>Syntax not understood
290 <option value="Rtalkback">Syntax not understood
291 Rev. TalkbackSyntax not understood
292 </option>Syntax not understood
293 </select></font></td>Syntax not understood
294 <td><font size="-2"><input type="submit" value="Update"></font></td>Syntax not understood
295 </tr>Syntax not understood
296 </table>Syntax not understood
297 </form>Syntax not understood
298 <center>Syntax not understood
299 <a name="highnews" id="highnews">&nbsp;</a><a href="/preferences.php3?area=topichigh">-= Highlighted stories above -- Normal news below =-</a>Syntax not understood
300 </center>Syntax not understood
301 <p></p>Syntax not understood
302 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
303 <tr>Syntax not understood
304 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
305 <a href="/story/2002-03-26-002-06-PS-PL-AD.html"><font size="4" face="arial,helvetica">perl.com: mod_perl in 30 minutes</font></a>Unknown directive
306 </td>Syntax not understood
307 </tr>Syntax not understood
308 </table><font size="1">(Mar 26, 2002, 19:43 UTC) (478 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
309 <font size="+0" face="arial,helvetica">"mod_perl in 30 minutes" article updated for apache_1.3.20 and mod_perl-1.26.</font>Syntax not understood
310 <p></p>Syntax not understood
311 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
312 <tr>Syntax not understood
313 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
314 <a href="/story/2002-03-26-001-06-PS-CY.html"><font size="4" face="arial,helvetica">Sun to allow open source Java implementations</font></a>Syntax not understood
315 </td>Syntax not understood
316 </tr>Syntax not understood
317 </table><font size="1">(Mar 26, 2002, 16:00 UTC) (723 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
318 <font size="+0" face="arial,helvetica">The Apache Software Foundation today announced that it has reached an agreement with Sun Microsystems and members of the Java Community Process to secure the basic right to implement Java specifications in open source.</font>Syntax not understood
319 <p></p>Syntax not understood
320 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
321 <tr>Syntax not understood
322 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
323 <a href="/story/2002-03-22-001-06-SC-CY-AD.html"><font size="4" face="arial,helvetica">SECURITY: Vulnerability in Apache for Win32 batch file processing</font></a>Unknown directive
324 </td>Syntax not understood
325 </tr>Syntax not understood
326 </table><font size="1">(Mar 22, 2002, 17:29 UTC) (1007 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
327 <font size="+0" face="arial,helvetica">Apache 1.3.24 was released. It fixes a remote command execution vulnerability.</font>Syntax not understood
328 <p></p>Syntax not understood
329 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
330 <tr>Syntax not understood
331 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
332 <a href="/story/2002-03-20-001-06-PS-PL.html"><font size="4" face="arial,helvetica">WebReference.com: mod_perl Developer's Cookbook</font></a>Unknown directive
333 </td>Syntax not understood
334 </tr>Syntax not understood
335 </table><font size="1">(Mar 20, 2002, 15:50 UTC) (895 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
336 <font size="+0" face="arial,helvetica">WebReference.com has published Chapter 4 from the newly released mod_perl Developer's Cookbook.</font>Syntax not understood
337 <p></p>Syntax not understood
338 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
339 <tr>Syntax not understood
340 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
341 <a href="/story/2002-03-13-002-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">mod_l33t added to Apache Module Registry</font></a>Syntax not understood
342 </td>Syntax not understood
343 </tr>Syntax not understood
344 </table><font size="1">(Mar 13, 2002, 21:09 UTC) (2799 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
345 <font size="+0" face="arial,helvetica">mod_l33t is a fast, memory-efficient, dynamic, and limited virtual hosting module for Apache.</font>Syntax not understood
346 <p></p>Syntax not understood
347 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
348 <tr>Syntax not understood
349 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
350 <a href="/story/2002-03-13-001-06-OS-SW-PH.html"><font size="4" face="arial,helvetica">Linux Easy Installer - Security Fixes</font></a>Syntax not understood
351 </td>Syntax not understood
352 </tr>Syntax not understood
353 </table><font size="1">(Mar 13, 2002, 21:02 UTC) (1571 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
354 <font size="+0" face="arial,helvetica">Linux Easy Installer package has been update to resolve upload PHP security problem.</font>Syntax not understood
355 <p></p>Syntax not understood
356 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
357 <tr>Syntax not understood
358 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
359 <a href="/story/2002-03-06-001-06-PS-DT-AD.html"><font size="4" face="arial,helvetica">Daemon News: Jakarta-Tomcat on FreeBSD 4.4</font></a>Unknown directive
360 </td>Syntax not understood
361 </tr>Syntax not understood
362 </table><font size="1">(Mar 6, 2002, 17:21 UTC) (3968 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
363 <font size="+0" face="arial,helvetica">"Servlets are small Java programs and are a better way to handle CGI tasks such as dynamic content and database interaction. Servlets run inside the Java Virtual Machine, which handles threads for each new request instead of the per instance model of traditional CGI programs. ... Tomcat is The Apache Group's reference implementation of a Servlet engine. It can handle both Servlets and JSPs. Tomcat can be run in stand-alone mode or with a HTTP server, such as Apache."</font>Syntax not understood
364 <p></p>Syntax not understood
365 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
366 <tr>Syntax not understood
367 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
368 <a href="/story/2002-03-05-001-06-OS-DT-PH.html"><font size="4" face="arial,helvetica">Moto, a compilable server-side scripting language</font></a>Syntax not understood
369 </td>Syntax not understood
370 </tr>Syntax not understood
371 </table><font size="1">(Mar 5, 2002, 01:05 UTC) (3357 reads) (2 talkbacks) (Posted by )</font><br>Unknown directive
372 <font size="+0" face="arial,helvetica">Moto is an embedded server-side scripting language first released about a year ago. Over the last few months, Moto has been undergoing heavy development. It has been ported to a wide variety of Unix platforms, including Mac OS X, Solaris, and FreeBSD, in addition to the many flavors of Linux it already ran on.</font>Syntax not understood
373 <p></p>Syntax not understood
374 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
375 <tr>Syntax not understood
376 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
377 <a href="/story/2002-03-01-001-06-SC-PH-AD.html"><font size="4" face="arial,helvetica">SECURITY: Flaws Found in PHP Leave Web Servers Open to Attack</font></a>Unknown directive
378 </td>Syntax not understood
379 </tr>Syntax not understood
380 </table><font size="1">(Mar 1, 2002, 18:56 UTC) (4145 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
381 <font size="+0" face="arial,helvetica">The Computer Emergency Response Team Coordination Center (CERT/CC) Wednesday warned of multiple vulnerabilities in the PHP scripting language that allow a remote attacker to execute arbitrary code with the privileges of the PHP process on a victim's system.</font>Syntax not understood
382 <p></p>Syntax not understood
383 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
384 <tr>Syntax not understood
385 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
386 <a href="/story/2002-02-26-002-06-PS-DP-AD.html"><font size="4" face="arial,helvetica">Everything Solaris: Apache: Handling Traffic</font></a>Unknown directive
387 </td>Syntax not understood
388 </tr>Syntax not understood
389 </table><font size="1">(Feb 26, 2002, 04:41 UTC) (4935 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
390 <font size="+0" face="arial,helvetica">"How you scale your infrastructure from here is wholly dependant on your growth needs and budget available. You will need to analyze your Website traffic and monitor your server performance characteristics closely to see how they all interelate."</font>Syntax not understood
391 <p></p>Syntax not understood
392 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
393 <tr>Syntax not understood
394 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
395 <a href="/story/2002-02-26-001-06-NW-CY-PH.html"><font size="4" face="arial,helvetica">LinuxEasyInstaller 2.0 final release</font></a>Syntax not understood
396 </td>Syntax not understood
397 </tr>Syntax not understood
398 </table><font size="1">(Feb 26, 2002, 04:36 UTC) (5545 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
399 <font size="+0" face="arial,helvetica">Linux Easy Installer is a script written in Perl that allows you to install quickly Apache, PHP, MySQL and phpMyAdmin. This script contains the sources of the programs, make the install and modify the configuration file.</font>Syntax not understood
400 <p></p>Syntax not understood
401 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
402 <tr>Syntax not understood
403 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
404 <a href="/story/2002-02-19-002-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Apache 2.0.32 beta is available</font></a>Syntax not understood
405 </td>Syntax not understood
406 </tr>Syntax not understood
407 </table><font size="1">(Feb 19, 2002, 23:31 UTC) (5261 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
408 <font size="+0" face="arial,helvetica">"The Apache HTTP Server Project is proud to announce the thirty-second release of Apache 2.0. The Apache HTTP Server Project has determined that this release is of beta quality. This makes 2.0.32 the third public beta of Apache 2.0. This release has been tested thoroughly and has been running the apache.org web site since Feb. 7, 2002."</font>Syntax not understood
409 <p></p>Syntax not understood
410 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
411 <tr>Syntax not understood
412 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
413 <a href="/story/2002-02-19-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Everything Solaris: Apache: The Basics</font></a>Unknown directive
414 </td>Syntax not understood
415 </tr>Syntax not understood
416 </table><font size="1">(Feb 19, 2002, 16:43 UTC) (4684 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
417 <font size="+0" face="arial,helvetica">"... In this article, we'll cover the very basics of Apache such as what it is and what it does, getting and installing it and properly configuring it to serve your first pages. Finally, some basic maintenance that you must do to keep everything running smoothly."</font>Syntax not understood
418 <p></p>Syntax not understood
419 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
420 <tr>Syntax not understood
421 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
422 <a href="/story/2002-02-06-003-06-PR-CY.html"><font size="4" face="arial,helvetica">Apache Jakarta James Mailserver v2.0a2 Released</font></a>Syntax not understood
423 </td>Syntax not understood
424 </tr>Syntax not understood
425 </table><font size="1">(Feb 6, 2002, 22:13 UTC) (6179 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
426 <font size="+0" face="arial,helvetica">James is a platform independant Java(tm) email and news server built using the Avalon application framenwork and supporting SMTP, POP3 and NNTP.</font>Syntax not understood
427 <p></p>Syntax not understood
428 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
429 <tr>Syntax not understood
430 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
431 <a href="/story/2002-02-06-002-06-NW-DB-PG.html"><font size="4" face="arial,helvetica">PostgreSQL v7.2 Final Release</font></a>Syntax not understood
432 </td>Syntax not understood
433 </tr>Syntax not understood
434 </table><font size="1">(Feb 6, 2002, 22:06 UTC) (31818 reads) (4 talkbacks) (Posted by )</font><br>Unknown directive
435 <font size="+0" face="arial,helvetica">"After almost a full year of development since PostgreSQL v7.1 was released, the PostgreSQL Global Development Group is proud to announce the availability of our latest development milestone ... PostgreSQL v7.2, another step forward for the project."</font>Syntax not understood
436 <p></p>Syntax not understood
437 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
438 <tr>Syntax not understood
439 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
440 <a href="/story/2002-02-06-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Daemon News: Multiple webservers behind one IP address</font></a>Unknown directive
441 </td>Syntax not understood
442 </tr>Syntax not understood
443 </table><font size="1">(Feb 6, 2002, 19:40 UTC) (8421 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
444 <font size="+0" face="arial,helvetica">"This article discusses a network setup where multiple webservers reside behind one IP address. Such a situation may arise when you need a specific webserver for one task and a different webserver for another task, running different operating systems or webserver software. With only one IP address available from the Internet, you could simply use Network Address Translation (NAT) with port forwarding. However, this forces you to give each webserver an ugly URL with a non-standard port number. Luckily, there is a better way. In the setup described in this article, each webserver can be reached via its own fully qualified domainname on the standard HTTP port (80)."</font>Syntax not understood
445 <p></p>Syntax not understood
446 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
447 <tr>Syntax not understood
448 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
449 <a href="/story/2002-02-04-001-06-PR-DT-AD.html"><font size="4" face="arial,helvetica">Zend Technologies launches Zend Studio 2.0</font></a>Syntax not understood
450 </td>Syntax not understood
451 </tr>Syntax not understood
452 </table><font size="1">(Feb 4, 2002, 18:38 UTC) (4652 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
453 <font size="+0" face="arial,helvetica">The "all-in-one" client-sever development package conveniently integrates all the applications developers need to code, debug and deploy advanced PHP e-commerce and business applications.</font>Syntax not understood
454 <p></p>Syntax not understood
455 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
456 <tr>Syntax not understood
457 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
458 <a href="/story/2002-01-31-001-06-PR-BZ-DT.html"><font size="4" face="arial,helvetica">NuSphere first to enable development of PHP web services</font></a>Syntax not understood
459 </td>Syntax not understood
460 </tr>Syntax not understood
461 </table><font size="1">(Jan 31, 2002, 02:44 UTC) (5506 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
462 <font size="+0" face="arial,helvetica">NuSphere offers integrated support for Apache, Perl, PHP and MySQL. NuSphere's PHPEd is an IDE (Integrated Development Environment) that integrates a comprehensive set of editing, debugging and deployment tools.</font>Syntax not understood
463 <p></p>Syntax not understood
464 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
465 <tr>Syntax not understood
466 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
467 <a href="/story/2002-01-28-001-06-PR-BZ-CY.html"><font size="4" face="arial,helvetica">Covalent Technologies raises $18 million in venture capital</font></a>Syntax not understood
468 </td>Syntax not understood
469 </tr>Syntax not understood
470 </table><font size="1">(Jan 28, 2002, 22:29 UTC) (3915 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
471 <font size="+0" face="arial,helvetica">Covalent Technologies, a leader in enterprise solutions for the Apache Web server, will use funds to expand sales and marketing efforts, and accelerate the company's growth in all business areas, including development of new enterprise management products.</font>Syntax not understood
472 <p></p>Syntax not understood
473 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
474 <tr>Syntax not understood
475 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
476 <a href="/story/2002-01-25-001-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Apache 1.3.23 released</font></a>Syntax not understood
477 </td>Syntax not understood
478 </tr>Syntax not understood
479 </table><font size="1">(Jan 25, 2002, 20:12 UTC) (7484 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
480 <font size="+0" face="arial,helvetica">The Apache Group has released version 1.3.23 of the Apache HTTP webserver. (No security vulnerabilities were addressed in this release.)</font>Syntax not understood
481 <p></p>Syntax not understood
482 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
483 <tr>Syntax not understood
484 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
485 <a href="/story/2002-01-24-001-06-PS-DT-MQ.html"><font size="4" face="arial,helvetica">wdvl: Build Your Own Database Driven Website Using PHP and MySQL: Part 4</font></a>Unknown directive
486 </td>Syntax not understood
487 </tr>Syntax not understood
488 </table><font size="1">(Jan 24, 2002, 18:17 UTC) (7158 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
489 <font size="+0" face="arial,helvetica">Learn how to install PHP and MySQL under Windows or Linux, as well as how to build a live Web-based content management system! This final installment covers publishing MySQL data on the Web, connecting to MySQL with PHP, sending SQL queries with PHP, inserting data into the database, and even has a "homework" assignment. From SitePoint.</font>Syntax not understood
490 <p></p>Syntax not understood
491 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
492 <tr>Syntax not understood
493 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
494 <a href="/story/2002-01-18-001-06-OS-BZ.html"><font size="4" face="arial,helvetica">Business 2.0: Find High Tech in the Bargain Basement</font></a>Unknown directive
495 </td>Syntax not understood
496 </tr>Syntax not understood
497 </table><font size="1">(Jan 18, 2002, 20:29 UTC) (4319 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
498 <font size="+0" face="arial,helvetica">Business 2.0 on Open Source and Apache as a Bargain</font>Syntax not understood
499 <p></p>Syntax not understood
500 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
501 <tr>Syntax not understood
502 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
503 <a href="/story/2002-01-10-001-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Another mod_xslt added to the Apache Module Registry database</font></a>Syntax not understood
504 </td>Syntax not understood
505 </tr>Syntax not understood
506 </table><font size="1">(Jan 10, 2002, 18:33 UTC) (4941 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
507 <font size="+0" face="arial,helvetica">An Apache module for parsing xml with an xsl was added to the Apache Module Registry.</font>Syntax not understood
508 <p></p>Syntax not understood
509 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
510 <tr>Syntax not understood
511 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
512 <a href="/story/2002-01-03-001-06-NW-BZ-CY.html"><font size="4" face="arial,helvetica">Netcraft Web Server Survey for December is available</font></a>Syntax not understood
513 </td>Syntax not understood
514 </tr>Syntax not understood
515 </table><font size="1">(Jan 3, 2002, 22:12 UTC) (5932 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
516 <font size="+0" face="arial,helvetica">Apache continues to be the top used web server with 56.50 percent. Microsoft IIS is used by 30.75 percent, according to the survey. According to Netcraft's research, Apache runs 20,497,607 sites.</font>Syntax not understood
517 <p></p>Syntax not understood
518 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
519 <tr>Syntax not understood
520 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
521 <a href="/story/2001-12-26-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">O'Reilly: Apache Web-Serving with Mac OS X: Part 1</font></a>Unknown directive
522 </td>Syntax not understood
523 </tr>Syntax not understood
524 </table><font size="1">(Dec 26, 2001, 19:26 UTC) (4692 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
525 <font size="+0" face="arial,helvetica">"Most people know that Mac OS X ships with a built-in Apache web server, but don't realize that it's easy to configure and run. In fact, you can host a web site in minutes after completing just a few simple steps. ..."</font>Syntax not understood
526 <p></p>Syntax not understood
527 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
528 <tr>Syntax not understood
529 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
530 <a href="/story/2001-12-14-001-06-PS-AD.html"><font size="4" face="arial,helvetica">WDVL: Perl for Web Site Management: Part 3</font></a>Unknown directive
531 </td>Syntax not understood
532 </tr>Syntax not understood
533 </table><font size="1">(Dec 14, 2001, 17:00 UTC) (4997 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
534 <font size="+0" face="arial,helvetica">This article shows how to write CGI scripts, incorporate search engines, convert multiple text files to HTML, monitor log files, and track visitors to your site. This third and final installment looks at storing the data, the "visit" data structure, and the &store_line subroutine.</font>Syntax not understood
535 <p></p>Syntax not understood
536 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
537 <tr>Syntax not understood
538 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
539 <a href="/story/2001-12-11-002-06-OS-DT-MQ.html"><font size="4" face="arial,helvetica">Retro web application framework V1.1.0 release</font></a>Syntax not understood
540 </td>Syntax not understood
541 </tr>Syntax not understood
542 </table><font size="1">(Dec 11, 2001, 21:37 UTC) (4103 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
543 <font size="+0" face="arial,helvetica">Retro uses Apache and the mod_fastcgi module to provide the same kind of web application development facilities as jsp/servlet environments, and the IIS ASP environment.</font>Syntax not understood
544 <p></p>Syntax not understood
545 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
546 <tr>Syntax not understood
547 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
548 <a href="/story/2001-12-11-001-06-PR-BZ-SW.html"><font size="4" face="arial,helvetica">Leveraging open standards such as Java, JSP, XML,J2EE, Expresso and Struts.</font></a>Syntax not understood
549 </td>Syntax not understood
550 </tr>Syntax not understood
551 </table><font size="1">(Dec 11, 2001, 21:35 UTC) (6315 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
552 <font size="+0" face="arial,helvetica">"Now based on both Expresso and Apache Jakarta Struts, this move makes Jcorporate the first and only vendor in its marketplace to be based on the two dominant OSS Java Web application development frameworks in use today, a shared standard jointly comprising an estimated 850f that market."</font>Syntax not understood
553 <p></p>Syntax not understood
554 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
555 <tr>Syntax not understood
556 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
557 <a href="/story/2001-12-04-002-06-NW-CY.html"><font size="4" face="arial,helvetica">Netcraft Web Server Survey for November is available</font></a>Syntax not understood
558 </td>Syntax not understood
559 </tr>Syntax not understood
560 </table><font size="1">(Dec 4, 2001, 17:59 UTC) (7737 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
561 <font size="+0" face="arial,helvetica">Apache continues to be the top used web server with 56.81 percent.</font>Syntax not understood
562 <p></p>Syntax not understood
563 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
564 <tr>Syntax not understood
565 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
566 <a href="/story/2001-12-04-001-06-NW-SW-DT.html"><font size="4" face="arial,helvetica">FoxServ 2.0 Released</font></a>Syntax not understood
567 </td>Syntax not understood
568 </tr>Syntax not understood
569 </table><font size="1">(Dec 4, 2001, 17:53 UTC) (5654 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
570 <font size="+0" face="arial,helvetica">After intensive beta stage testing and some feedback, we are proud to present FoxServ 2.0. This version has changed a lot since beta 3. It has fixed the configurator issue on php and added MySQL frontend and Python 2.1.</font>Syntax not understood
571 <p></p>Syntax not understood
572 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
573 <tr>Syntax not understood
574 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
575 <a href="/story/2001-11-30-002-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Ace's Hardware: Building a Better Webserver in the 21st Century</font></a>Unknown directive
576 </td>Syntax not understood
577 </tr>Syntax not understood
578 </table><font size="1">(Nov 30, 2001, 20:12 UTC) (6880 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
579 <font size="+0" face="arial,helvetica">"Our old web application was written in PHP and ran on Apache, a "pre-fork" multiprocess HTTP server. Apache works by starting a parent process which then forks several child processes to listen and wait for HTTP connections. Since, each of these child processes serves one HTTP request at a time, Apache creates a pool of processes to handle connections in a timely fashion." This article talks about the hardware and software changes when upgrading a webserver. They end up using an alternative to Apache.</font>Syntax not understood
580 <p></p>Syntax not understood
581 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
582 <tr>Syntax not understood
583 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
584 <a href="/story/2001-11-30-001-06-PS-CY-AD.html"><font size="4" face="arial,helvetica">Web Techniques: Customer Number One</font></a>Unknown directive
585 </td>Syntax not understood
586 </tr>Syntax not understood
587 </table><font size="1">(Nov 30, 2001, 19:54 UTC) (4705 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
588 <font size="+0" face="arial,helvetica">"Whether you're administering a single, dedicated Web server, or one serving hundreds of hosts, each site's client expects and deserves a certain level of support and service. ..." This article covers mod_throttle, having each site operate under its own user ID, and running several instances of Apache.</font>Syntax not understood
589 <p></p>Syntax not understood
590 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
591 <tr>Syntax not understood
592 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
593 <a href="/story/2001-11-27-002-06-NW-CY-AD.html"><font size="4" face="arial,helvetica">Apache-Frontpage RPM project updated</font></a>Syntax not understood
594 </td>Syntax not understood
595 </tr>Syntax not understood
596 </table><font size="1">(Nov 27, 2001, 21:57 UTC) (7196 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
597 <font size="+0" face="arial,helvetica">This project makes it easier for new people to get FrontPage 2002 extensions running with Apache. It is now updated to use Apache 1.3.22.</font>Syntax not understood
598 <p></p>Syntax not understood
599 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
600 <tr>Syntax not understood
601 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
602 <a href="/story/2001-11-27-001-06-PS-CY.html"><font size="4" face="arial,helvetica">CNet: Open-source approach fades in tough times</font></a>Unknown directive
603 </td>Syntax not understood
604 </tr>Syntax not understood
605 </table><font size="1">(Nov 27, 2001, 20:15 UTC) (2682 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
606 <font size="+0" face="arial,helvetica">"On the business end, companies typically seek customers with the free software and derive revenue by selling services and support. ... But that's proved easier said than done."</font>Syntax not understood
607 <p></p>Syntax not understood
608 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
609 <tr>Syntax not understood
610 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
611 <a href="/story/2001-11-16-002-06-PS-BZ.html"><font size="4" face="arial,helvetica">NewsForge: VA spin-off releases first product, aims for profit</font></a>Unknown directive
612 </td>Syntax not understood
613 </tr>Syntax not understood
614 </table><font size="1">(Nov 16, 2001, 20:19 UTC) (3036 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
615 <font size="+0" face="arial,helvetica">"XAO Inc., a privately held spin off of VA Linux, announced the release of the XAO 1.0 Web server, a Web-services software package based on Apache."</font>Syntax not understood
616 <p></p>Syntax not understood
617 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
618 <tr>Syntax not understood
619 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
620 <a href="/story/2001-11-16-001-06-NW-CY-DP.html"><font size="4" face="arial,helvetica">Apache 2.0.28 Released as Beta</font></a>Syntax not understood
621 </td>Syntax not understood
622 </tr>Syntax not understood
623 </table><font size="1">(Nov 16, 2001, 19:05 UTC) (5696 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
624 <font size="+0" face="arial,helvetica">"The Apache Group is proud to announce the twenty-eighth release of Apache 2.0. This is the second public beta of Apache 2.0. This release has been tested thoroughly and has been running the apache.org web site since Nov. 9, 2001."</font>Syntax not understood
625 <p></p>Syntax not understood
626 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
627 <tr>Syntax not understood
628 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
629 <a href="/story/2001-11-12-001-06-PR-BZ-CY.html"><font size="4" face="arial,helvetica">Covalent Technologies announces industry support for Enterprise Ready Server and Apache 2.0</font></a>Syntax not understood
630 </td>Syntax not understood
631 </tr>Syntax not understood
632 </table><font size="1">(Nov 12, 2001, 20:52 UTC) (3726 reads) (1 talkbacks) (Posted by )</font><br>Unknown directive
633 <font size="+0" face="arial,helvetica">"In conjunction with the launch of Enterprise Ready Server, Covalent Technologies today announced a coalition of support for its new enterprise solution for the Apache Web server. A wide range of companies support the new software product designed to enhance the reliability, security and manageability of the world's most widely used Web server."</font>Syntax not understood
634 <p></p>Syntax not understood
635 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
636 <tr>Syntax not understood
637 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
638 <a href="/story/2001-11-07-001-06-PS-PH-AD.html"><font size="4" face="arial,helvetica">developer.com: On the Security of PHP, Part 1</font></a>Unknown directive
639 </td>Syntax not understood
640 </tr>Syntax not understood
641 </table><font size="1">(Nov 7, 2001, 13:56 UTC) (4914 reads) (3 talkbacks) (Posted by )</font><br>Unknown directive
642 <font size="+0" face="arial,helvetica">Despite the fact that PHP is designed with security in mind, a familiarity with its more dangerous aspects and conformance to common secure programming guidelines is essential to minimizing the possibility of security compromises. The aim of this document is to provide an overview of various security issues with PHP and to offer advice on secure PHP programming practices.</font>Syntax not understood
643 <p></p>Syntax not understood
644 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
645 <tr>Syntax not understood
646 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
647 <a href="/story/2001-11-06-001-06-PR-DP-MQ.html"><font size="4" face="arial,helvetica">Apache/PHP-based Content Management System Release</font></a>Syntax not understood
648 </td>Syntax not understood
649 </tr>Syntax not understood
650 </table><font size="1">(Nov 6, 2001, 12:33 UTC) (8741 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
651 <font size="+0" face="arial,helvetica">Digital Spinner, a web design and applications development company, announced today the fifth release candidate<br>Syntax not understood
652 of the GroupIT Engine, a PHP-based content management and group collaboration system capable of powering the next generation of web sites, intranets and extranets.</font>Syntax not understood
653 <p></p>Syntax not understood
654 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
655 <tr>Syntax not understood
656 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
657 <a href="/story/2001-11-05-001-06-PR-BZ-AD.html"><font size="4" face="arial,helvetica">HyperSpace Communications announces limited release of HyperSpace Accelerator software</font></a>Syntax not understood
658 </td>Syntax not understood
659 </tr>Syntax not understood
660 </table><font size="1">(Nov 5, 2001, 17:42 UTC) (3675 reads) (0 talkbacks) (Posted by )</font><br>Unknown directive
661 <font size="+0" face="arial,helvetica">"HyperSpace enables content providers to dramatically accelerate the transmission and receipt of data over the Internet through a sharp reduction in bandwidth requirement. ... HyperSpace is the full-featured, commercial version of what began as Mod_gzip, a free, downloadable module the Company began offering a year ago to users of Apache servers."</font>Syntax not understood
662 <p></p>Syntax not understood
663 <center>Syntax not understood
664 <a name="normalnews" id="normalnews">&nbsp;</a><a href="/preferences.php3?area=topiclow">-= Filtered [less interesting] news below =-</a>Syntax not understood
665 </center>Syntax not understood
666 <p></p>Syntax not understood
667 <center>Syntax not understood
668 <a name="boringnews" id="boringnews">&nbsp;</a><a href="/preferences.php3?area=topichigh">-= Highlighted=0 Regular=40 Boring=0 =-<br>Syntax not understood
669 -= Click here to change filter settings =-</a>Syntax not understood
670 </center>Syntax not understood
671 <p></p>Syntax not understood
672 </td>Syntax not understood
673 <td width="20%" valign="top" align="right">Syntax not understood
674 <table border="0" width="100%">Syntax not understood
675 <tr>Syntax not understood
676 <td>Syntax not understood
677 <form method="post" action="/account.php3">Syntax not understood
678 <table align="center" border="0">Syntax not understood
679 <tr>Syntax not understood
680 <td colspan="2"><font size="-1">Your Apache Today<br>Syntax not understood
681 <a href="/about.php3#YLT"><b>Find Out Why!</b></a></font></td>Syntax not understood
682 </tr>Syntax not understood
683 <tr>Syntax not understood
684 <td><font size="-1">Login</font></td>Syntax not understood
685 <td><input type="text" size="8" name="username"></td>Syntax not understood
686 </tr>Syntax not understood
687 <tr>Syntax not understood
688 <td><font size="-1">Password</font></td>Syntax not understood
689 <td><input type="password" size="8" name="passwd"></td>Syntax not understood
690 </tr>Syntax not understood
691 <tr>Syntax not understood
692 <td><input type="submit" name="login" value="Login"></td>Syntax not understood
693 <td><input type="submit" name="create" value="Create"> <input type="hidden" name="redirect" value=""> <input type="hidden" name="loginboxtag" value="loginbox"></td>Syntax not understood
694 </tr>Syntax not understood
695 </table>Syntax not understood
696 </form>Syntax not understood
697 </td>Syntax not understood
698 </tr>Syntax not understood
699 </table>Syntax not understood
700 <p></p>Syntax not understood
701 <center>Syntax not understood
702 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/1423649654/125x125-1/House_ISP_Expo_3x/ispbusexpo_125_new.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/House_ISP_Expo_3x/ispbusexpo_125_new.gif" width="125" height="125" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/1423649654/125x125-1/House_ISP_Expo_3x/ispbusexpo_125_new.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
703 </center>Syntax not understood
704 <p></p>Syntax not understood
705 <div align="left">Syntax not understood
706 <font size="+1" face="arial,helvetica"><b>Latest Feature</b></font>Syntax not understood
707 <p></p>Syntax not understood
708 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
709 <tr>Syntax not understood
710 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
711 <a href="https://www.ssl.org"><font size="3" face="arial,helvetica">SSL checker</font></a>Unknown directive
712 </td>Syntax not understood
713 </tr>Syntax not understood
714 </table>Apache mod_ssl is a web server module that helps in providing secure communication via TLS protocols. Verify TLS/SSL certificate installation errors.<br>Syntax not understood
715 (August 12, 2024) <p></p>Syntax not understood
716 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
717 <tr>Syntax not understood
718 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
719 <a href="/news_story.php3?ltsn=2000-06-30-002-01-NW-LF-SW"><font size="3" face="arial,helvetica">Looking at Apache 2.0 Alpha 4</font></a>Syntax not understood
720 </td>Syntax not understood
721 </tr>Syntax not understood
722 </table>Development continues to roll along on Apache 2.0. In his latest column, Ryan Bloom details what's new in the recently released Apache 2.0 Alpha 4.<br>Syntax not understood
723 (Jun 30, 2000)Syntax not understood
724 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
725 <tr>Syntax not understood
726 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
727 </tr>Syntax not understood
728 </table><font size="+1" face="arial,helvetica"><b>Apache Today Features</b></font>Syntax not understood
729 <p></p>Syntax not understood
730 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
731 <tr>Syntax not understood
732 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
733 <a href="/news_story.php3?ltsn=2000-09-27-001-01-OP-CY-LF"><font size="3" face="arial,helvetica">The Apache Web Server Documentation Project</font></a>Syntax not understood
734 </td>Syntax not understood
735 </tr>Syntax not understood
736 </table>Over the years, a lot of people have become interested in the idea of contributing to the Apache HTTP Server project, but have hung back or remained silent because they felt only hardcore C programmers with tons of experience need apply. Some actually have contacted the Project, saying they'd like to help out but don't have the coding skills and so didn't know what they could do. And some have offered specifically to help out on the documentation, either translating it, or correcting technical nits, or improving its readability or navigability. In July of 2000, however, the Apache HTTP server project created a subproject and reorganised the documentation files so that they can be worked on directly by non-programmers. This article describes more about this, and how you can get involved.<br>Syntax not understood
737 (Sep 27, 2000)Syntax not understood
738 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
739 <tr>Syntax not understood
740 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
741 </tr>Syntax not understood
742 </table>Syntax not understood
743 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
744 <tr>Syntax not understood
745 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
746 <a href="/news_story.php3?ltsn=2000-06-14-002-01-PS"><font size="3" face="arial,helvetica">Keeping Your Images from Adorning Other Sites</font></a>Syntax not understood
747 </td>Syntax not understood
748 </tr>Syntax not understood
749 </table>Webmasters are ever searching for ways to make their sites look cool and attractive. One way is to dress it up with images, logos, and other graphics--sometimes referred to as 'eye candy.' Of course, if you happen to be in the forefront of this in any way, you run the risk of having others cadge <i>your</i> art in order to dress up <i>their</i> sites. This article shows how you can use Apache configuration directives to limit access to your art so that it's more difficult to use elsewhere.<br>Syntax not understood
750 (Jun 14, 2000)Syntax not understood
751 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
752 <tr>Syntax not understood
753 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
754 </tr>Syntax not understood
755 </table>Syntax not understood
756 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
757 <tr>Syntax not understood
758 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
759 <a href="/news_story.php3?ltsn=2000-05-31-001-08-NW-LF"><font size="3" face="arial,helvetica">E-Commerce Solutions: An Apache Overview</font></a>Unknown directive
760 </td>Syntax not understood
761 </tr>Syntax not understood
762 </table>With this column Martin C. Brown begin his regular coverage of Apache and E-Commerce for Apache Today. This initial column maps out the burgeoning area of E-Commerce and what every Apache Webmaster needs to know about implementing E-Commerce on their site.<br>Syntax not understood
763 (May 31, 2000)Syntax not understood
764 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
765 <tr>Syntax not understood
766 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
767 </tr>Syntax not understood
768 </table>Syntax not understood
769 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
770 <tr>Syntax not understood
771 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
772 <a href="/news_story.php3?ltsn=2000-05-28-004-01-PS"><font size="3" face="arial,helvetica">An Introduction to Apache 2.0</font></a>Syntax not understood
773 </td>Syntax not understood
774 </tr>Syntax not understood
775 </table>Apache 2.0 has already been through three alpha releases. In this preview, Ryan Bloom of the Apache Group previews Apache 2.0 and explains why it will make life easier for every Webmaster on the Internet.<br>Syntax not understood
776 (May 28, 2000)Syntax not understood
777 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
778 <tr>Syntax not understood
779 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
780 </tr>Syntax not understood
781 </table>Syntax not understood
782 <table width="99%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
783 <tr>Syntax not understood
784 <td valign="top" bgcolor="#EEEEEE">Syntax not understood
785 <a href="/news_story.php3?ltsn=2000-06-1-001-01-NW-DP-LF"><font size="3" face="arial,helvetica">Getting Started with Apache 1.3</font></a>Syntax not understood
786 </td>Syntax not understood
787 </tr>Syntax not understood
788 </table>While you're licking your chops and waiting for Apache 2.0 to be released, you're probably facing a very real situation of having to set up an Apache Web server today. In this overview, Apache pioneer Ken Coar goes through all the steps needed to install and configure an Apache 1.3 Web server.<br>Syntax not understood
789 (Jun 1, 2000)Syntax not understood
790 <table width="100%" cellpadding="0" cellspacing="0" border="0">Syntax not understood
791 <tr>Syntax not understood
792 <td valign="top" bgcolor="white">&nbsp;</td>Syntax not understood
793 </tr>Syntax not understood
794 </table>Syntax not understood
795 </div>Syntax not understood
796 <p></p>Syntax not understood
797 <div align="left"></div>Syntax not understood
798 <div align="left">Syntax not understood
799 <p></p>Syntax not understood
800 <table cellspacing="1" cellpadding="4" border="0" width="100%">Syntax not understood
801 <tr>Syntax not understood
802 <td valign="middle" align="center"><b>www.BSDtoday.com</b></td>Syntax not understood
803 </tr>Syntax not understood
804 <tr>Syntax not understood
805 <td>"Linux Journal: Why I Don't Use the GPL<br>Unknown directive
806 ""It has Excel and Word"<br>Syntax not understood
807 "ZDNet: Want a Windows alternative? Try BSD<br>Unknown directive
808 "Changes to the NetBSD Packages Collection in February 2002<br>Syntax not understood
809 "Linux and main: Running a corporation in an open source world<br>Unknown directive
810 "Linux Journal: Hardening Sendmail<br>Unknown directive
811 "OSNews: Understanding CVSup, Mounting, Ports and Init on FreeBSD<br>Unknown directive
812 "ONLamp: BSDCon 2002<br>Unknown directive
813 "Wind River announces product rollout plans for future BSD/OS releases<br>Syntax not understood
814 "Wind River announces BSD/OS 4.3 release<br></td>Syntax not understood
815 </tr>Syntax not understood
816 </table>Syntax not understood
817 <p></p>Syntax not understood
818 <table cellspacing="1" cellpadding="4" border="0" width="100%">Syntax not understood
819 <tr>Syntax not understood
820 <td valign="middle" align="center"><b>PHPBuilder.com New Articles</b></td>Syntax not understood
821 </tr>Syntax not understood
822 <tr>Syntax not understood
823 <td>"Getting started with php and InterBase<br>Syntax not understood
824 "Configuring PHP with ORACLE 8i Support<br>Syntax not understood
825 "Using PHP and MySQL with Flash<br>Syntax not understood
826 "Making PHP Applications Cache-Friendly<br>Syntax not understood
827 "Making forms object-oriented<br>Syntax not understood
828 "PHP programming methodologies and documentation<br>Syntax not understood
829 "Using Webalizer to analyze Apache logs<br>Syntax not understood
830 "Optimizing Postgresql<br>Syntax not understood
831 "Getting Started with PHP/Ming<br>Syntax not understood
832 "Cross-platform and Portable Development With PHP<br></td>Syntax not understood
833 </tr>Syntax not understood
834 </table>Syntax not understood
835 <p></p>Syntax not understood
836 <table cellspacing="1" cellpadding="4" border="0" width="100%">Syntax not understood
837 <tr>Syntax not understood
838 <td valign="middle" align="center"><b>Linux Today</b></td>Syntax not understood
839 </tr>Syntax not understood
840 <tr>Syntax not understood
841 <td>Syntax not understood
842 <center>Syntax not understood
843 <p><img src="http://linuxtoday.com/pics/ltnet.png" alt="Linux Today" border="0"></p>Unknown directive
844 </center>Syntax not understood
845 <p>"NewsForge: A Tale of Two Linux Bootable Business Cards<br>Unknown directive
846 "Java.Sun.com: Java Community Process Embraces Open Source<br>Unknown directive
847 "Computerworld New Zealand: Linux Wannabes Get Help<br>Unknown directive
848 "ZDNet UK: Stallman: Patents Victimize Developers<br>Unknown directive
849 "Linux Weekly News for March 28, 2002<br></p>Syntax not understood
850 <form method="get" action="http://linuxtoday.com/search.php3">Unknown directive
851 Search Linux Today:<br>Unknown directive
852 <input type="text" name="query"><br>Syntax not understood
853 <input type="submit" value="Search">Syntax not understood
854 </form>Syntax not understood
855 </td>Syntax not understood
856 </tr>Syntax not understood
857 </table><font size="-1"></font>Syntax not understood
858 <center>Syntax not understood
859 <a href="/preferences.php3?area=upflag2"><font size="-1">Content settings.</font></a>Syntax not understood
860 </center>Syntax not understood
861 </div>Syntax not understood
862 </td>Syntax not understood
863 </tr>Syntax not understood
864 </table>Syntax not understood
865 <table align="center" border="0" cellpadding="10" cellspacing="0">Syntax not understood
866 <tr>Syntax not understood
867 <td align="center">Syntax not understood
868 <img height="17" width="120" src="/pics/icom-micros.png" border="0" alt="To internet.com">Syntax not understood
869 <p></p>Syntax not understood
870 </td>Syntax not understood
871 </tr>Syntax not understood
872 <tr>Syntax not understood
873 <td>Syntax not understood
874 <center>Syntax not understood
875 <a href="/RealMedia/ads/click_lx.cgi/intm/linux/apachetoday.com/index/934345979/468x60-2/Covalent_Technologies_4b/new_ERS_seminar_750x100.gif/64316637323836333363613433343230" target="_top"><img src="/RealMedia/ads/Creatives/Covalent_Technologies_4b/new_ERS_seminar_750x100.gif" alt="" border="0"></a><img src="/RealMedia/ads/adstream_lx.cgi/intm/linux/apachetoday.com/index/934345979/468x60-2/Covalent_Technologies_4b/new_ERS_seminar_750x100.gif/64316637323836333363613433343230?_RM_EMPTY_" width="1" height="1" border="0">Syntax not understood
876 </center>Syntax not understood
877 </td>Syntax not understood
878 </tr>Syntax not understood
879 </table>Syntax not understood
880 <center>Syntax not understood
881 <script language="javascript" src="http://ss.webring.yahoo.com/navbar?f=j&y=paulmferris&u=97084277210026050"></script>Unknown directive
882 </center>Syntax not understood
883 <table bgcolor="#0044DE" width="100%">Syntax not understood
884 <tr align="center">Syntax not understood
885 <td bgcolor="#FF3300">Syntax not understood
886 <a href="/triggerFAQ.php3"><font color="#FFFFFF"><b>About Triggers</b></font></a>Syntax not understood
887 </td>Syntax not understood
888 <td bgcolor="#DD7400">Syntax not understood
889 <a href="/mediakit.php3"><font color="#FFFFFF"><b>Media Kit</b></font></a>Syntax not understood
890 </td>Syntax not understood
891 <td bgcolor="#999900">Syntax not understood
892 <a href="/index.php3?override=64"><font color="#FFFFFF"><b>Security</b></font></a>Syntax not understood
893 </td>Syntax not understood
894 <td bgcolor="#00BB44">Syntax not understood
895 <a href="/trigger.php3"><font color="#FFFFFF"><b>Triggers</b></font></a>Syntax not understood
896 </td>Syntax not understood
897 <td bgcolor="#009999">Syntax not understood
898 <a href="/account.php3"><font color="#FFFFFF"><b>Login</b></font></a>Syntax not understood
899 </td>Syntax not understood
900 </tr>Syntax not understood
901 </table>Syntax not understood
902 <p></p>Syntax not understood
903 <table border="0" cellpadding="3" cellspacing="0" bgcolor="#FFFFFF" width="100%">Syntax not understood
904 <tr>Syntax not understood
905 <td align="center">Syntax not understood
906 <font size="2" face="Arial, Helvetica, sans-serif"><br>Syntax not understood
907 All times are recorded in UTC.<br>Syntax not understood
908 Linux is a trademark of Linus Torvalds.<br>Syntax not understood
909 Powered by Linux 2.4, Apache 1.3, and PHP 4</font>Syntax not understood
910 <center>Syntax not understood
911 <font size="2" face="Arial, Helvetica, sans-serif"><span class="foot">Copyright 2002 INT Media Group, Incorporated All Rights Reserved.</span><br>Syntax not understood
912 Legal Notices, �Licensing, Reprints, & Permissions, �Privacy Policy.<br>Syntax not understood
913 <img src="/img/URL.gif" alt="http://www.internet.com/" width="161" height="18" border="0"></font>Unknown directive
914 </center><font size="2" face="Arial, Helvetica, sans-serif"></font>Syntax not understood
915 </td>Syntax not understood
916 </tr>Syntax not understood
917 </table>Syntax not understood
918 </center>Syntax not understood
919 </center>Syntax not understood
920</body>Syntax not understood
921</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback