Apache Week
Issue 203, 16thJune2000:

Copyright 2020 Red Hat, Inc

In this issue

Appaloosa Awards reward Apache innovation

The Appaloosa Awards are this year's new awards to acknowledge the efforts of those who the Apache community believe to have had the most significant influences on the Apache Software Foundation's open-source projects.

O'Reilly's "White Camel" awards last year went a long way to praising the Perl community's "unsung heroes" - those who devoted extraordinary creativity, energy, and time to the non-technical work that supports Perl's user community. That's exactly the ethos the ASF are trying to capture with this new Apache-specific version of the contest.

The nominations are complete and voting is now open in one of the following categories:

  • Vision Award - best ideas of how to move Apache forward
  • Evangelism Award - promoting Apache awareness or acceptance
  • Technical Contribution Award - New ideas, bug fixes, new modules

July's O'Reilly Open Source conference plays host to the awards ceremony on 18th July in Monterey, California and Apache Week will be there to cover the ceremony and the conference.

The web-based voting system for the awards is being hosted by Apache Week and is open until midnight 22nd June (GMT). Vote now!

Featured Articles

The Developer Shed's new article, "WAP Enabling A Web Site With PHP3". builds on a case study previously featured in Apache Week which explains how to simplify content for delivery to WAP-enabled devices. Interactive sites can be simplified by separating data management from the site presentation and then parsing content through PHP before returning it to the client. This means that support for WAP browsing - using a device such as a Nokia 7110 or a net-connected Palm device - can be added easily to an existing site that has been thought out properly.

In "Keeping Your Images from Adorning Other Sites", Ken Coar looks at how the addition of a few simple directives can stop other sites from poaching your work by accessing images directly by URL in their source. This is made possible by using the referer header which is sent by most browsers and includes the URL of the resource previously visited. By checking this header you can see which sites are linking directly to your resources and stop them. The example in the article will however also stop accesses when this header is missing from a request, a behaviour that is not ideal. Some older browsers do not send this header, and many proxies (such as the Anonymizer) strip the header due to privacy concerns.