Free 404 software for linux

• A Firewall with stateful packet inspection and application proxies guards Internet communications traffic in and out of the organization.
• A Virtual Private Network (VPN) gateway assures secure communications with remote offices, road warriors and telecommuters.
• Anti-Virus defends computers from both email and web-bourne viruses.
• Intrusion Protection detects and stops hostile probes and application-based attacks.
• Spam Filtering eliminates the productivity drain of opening and deleting unsolicited emails.
• Surf Protection (Content Filtering) and Spyware Protection improve productivity by blocking inappropriate web activities, provide full protection from user tracking threats and violation of privacy.

Major Features:

1. Protects all types of networks Windows, Linux, Unix and others.
2. Delivers comprehensive features at low cost maximizing your ROI (return on investment).
3. Highly effective. Has won numerous industry awards. Beat Cisco and Checkpoint in InfoWorld magazine product review, Beat IBM and Computer Associates in Linux World for Best Security Application.
4. Integrated management platform features an intuitive browser-based interface and one-step updates for rapid deployment and easy management.
5. Can be installed in under 15 minutes or purchased pre-installed on security appliances.
6. Can start with firewall, VPN and spam protection and add other security applications as needed, seamlessly.
7. Runs as a dedicated application server on top of a hardened operating system, which relieves operating system management headaches.
8. Runs on systems ranging from small devices up to large multi-processor systems utilizing gigabytes of memory.
9. Redundant systems can be configured to provide high availability and automatic failover in case of hardware or network failures.
10. Load balancing improves performance traffic shaping can set priorities by network, service and protocol.
11. Logging, automatic backup, and diagnostic tools support high reliability.
12. Free online evaluation workshop to get you started.

Enhancements:

• This Up2Date addresses a few issues that did not make the 7.4 GA version in time.
• This is a pure bugfix/stability release that strengthens the quality of your installation.

Major Features:

1. Request dispatching: Map requests to handler-callables using URL-routes.
2. URL parameters: Use regular expressions /object/(?P[0-9]+) or simplified syntax /object/:id to extract data out of URLs.
3. WSGI abstraction: Dont worry about cgi and wsgi internals.
4. Input: request.GET[parameter] or request.POST[form-field]
5. HTTP header: response.header[Content-Type] = text/html.
6. Cookie Management: response.COOKIES[session] = new_key.
7. Static files: send_file(movie.flv, /downloads/) with automatic mime-type guessing.
8. Errors: Throw HTTP errors using abort(404, Not here) or subclass HTTPError and use custom error handlers.
9. Templates: Integrated template language.
10. Plain simple: Execute python code with %... or use the inline syntax {{...}} for one-line expressions.
11. No IndentationErrors: Blocks are closed by %end. Indentation is optional.
12. Extremely fast: Parses and renders templates 5 to 10 times faster than mako.
13. Support for Mako-Templates (requires mako).
14. HTTP Server: Build in WSGI/HTTP Gateway server (for development and production mode)
15. Currently supports wsgiref.simple_server (default), cherrypy, flup, paste and fapws3.
16. Speed optimisations:

Requirements:

• Python

jPOS project is a Java based, production grade ISO-8583 library/framework that can be used to implement financial interchanges, protocol converters, payment gateways, credit card verification clients and servers (merchant/issuer/acquirer), etc.
Enhancements:
- Upgrade to jdom-1.0.jar
- Changed LogEvent to support new jdom version
- Upgraded build system (uses jPOS-EEs approach
- Added DailyLogListener
- Use crimson instead of xerces
- Created compat_1_5_2 module
- Upgraded jdbm to 1.0
- transient:* and persistent:* Spaces urns now maps to TSpace and JDBMSpace
- ISOMsg writeExternal and readExternal now honors packager if available
- ISOMsg.set(int,String) can be used for ISOBinaryFields provided theres a packager associated with the ISOMsg (the string is interpreted as hex)
- Added appropriate thread names
- TransactionManager stuff moved to its own module txnmgr
- BaseChannel.disconnect closes socket before closing streams (better SSL behaveour)
- ISOServer do not drop connection on VetoException
- bugfix in Log4JListener (if watch=0 use default watch to avoid CPU going up to 100%
- TSpace and JDBMSpace throws NPE at out time if either key or value are null
- ISOCurrencys data moved to a ResourceBundle
- Dump hexstring of binary fields in ISOBasePackager.unpack
- Added IFE_AMOUNT
- Added TransactionManager debug property
- TransactionManager creates default persistent-space if one is not specified
- TransactionManager honors participants configured after group selectors
- TransactionManager now support RETRY action at prepare time (r2359)
- QServer.stop - avoid npe on unstarted/misconfigured servers (r2360)
- ISOChannelPanel now supports wipe and protect attributes (r2363)
- Added IFE_SIGNED_NUMERIC and SignedEbcdicNumberInterpreter
- Added sendKeepAlive() method to BaseChannel
- New ?keep-alive? element in ChannelAdaptor
- FSDMsg trunk fields bigger than length
- Reworked 3rd bitmap support
- QMUX now support multiple ready indicators
- NPE in Q2 startup when deploy directory is not available/readable
- ISOServer now honors new keep-channels property (true|false)
- Added bind-address and backlog properties to ISOServer
- ISOServer: close ThreadPool on shutdown
- FSDMsg truncate A fields larger than length
- synchronized NameRegistrar
- GenericSubFieldPackager - pack dummy fields if field is not available and inner message has no bitmap
- QMUX now supports new .. configuration element (defaults to 41, 11 ).
- Added org.jpos.transaction.participant.HasEntry general purpose Group Selector
- TransactionManager attempts to call setTransactionManager(TransactionManager) on participants
- Bugfix in IF_TCHAR (unpack offset - r2410)
- Added Q2.shutdown (boolean join) (r2414)
- Added Join participant (r2416)
- Added keep-alive property to BaseChannel (r2417) - feature request #404
- Include a call to tx & rx.interrupt so that an idle ISOMUX will honour terminate requests.
- added setOverrideHeader(boolean) and isOverrideHeader() to BaseChannel
- ISOUtil.normalize uses UTF-8 encoding
- BaseChannel: added protected int getHeaderLength(ISOMsg m)
- TransactionManager.stop() wait (via join) for sessions to terminate (r2422)
- ISOServer/ThreadPool: Added socket closure in the event of ThreadPool exhaustion. Combined with a tightening of count of active, working and available Threads in ThreadPool itself (r2423).
- Added IFA_LLLLLLCHAR field packager (r2424)
- Bugfix in DailyTaskAdaptor in order to deal with daylight saving change (r2425)
- XMLPackager honors optional ... element at unpack time. (r2426)
- bugfix in ChannelAdaptor: honor reconnect delay on peer-disconnect exceptions (r2429)
- Added new configuration element to QMUX (r2432)
- genericpackager.dtd - added optional firstField element to fieldpackager and isofieldpackager (r2434)
- QMUX added removeISORequestListener (r2435)
- IFB_LLLHCHAR, IFB_LLLHECHAR and IFB_LLLHBINARY length can go up to 65535 (r2437)
- ISOBasePackager - add support for composite MTIs (r2438)
- BaseChannel accepts new max-packet-length optional property - new default size 100k (r2441)
- bugfix: ISOServer clones max-packet-length
- Added new MUXPool component (r2443)
- TransactionManager minor optimization - do not take snapshot if psp is not actually persistent (r2444)
- SpaceUtil new wipeAndOut helpers (r2447)
- TransactionManager - new PAUSE support (r2448)
- bugfix: GZipChannel compressed/uncompressed length (r2458)
- TransactionManager new method getOutstandingTransactions (r2459)
- added org.jpos.transaction.participant.Forward (r2459)
- added org.jpos.transaction.participant.CheckPoint (r2460)
- QFactory.properties added txnmgr and transaction-manager aliases (r2462)

apt-got is a customizable Debian local mirror engine. It works like a highly specialized proxy.
It employs several pluggable modules that are customized for specific jobs.
The first available module builds and supervises a partial (or full) Debian mirror which is populated on-the-fly by apt-get requests.
There is also a simple mirror module that can be used to mirror source directories or even (static) Web pages.
To save bandwidth our program will function like a drop-in, stand-alone proxy for the internal network.
But in addition it will store already requested packages locally.
Packages that are not yet stored locally are fetched upon client-request from the parent server transparently.
Main features:
- Reduce bandwidth usage
- Reduce download time
- Handle client request
- Respond to request from client
- Request files from remote server
- Handle server responses (e.g. file not found404, etc.)
- Cache files locally
- If multiple clients request a specific file simultaneously, download only once from remote server
- Handle disk usage (purge old files)
Enhancements:
- SimpleMirrorFile gets cached until the next Purger run. Removed bug that prevented the server from sending a 404 instead it sended a 0 length file.
- Fixed bug with MirrorFileState in DebianMirrorFile.
- Cleaned up logger infrastructure.

pyctures is a small web gallery written in Python that uses the web.py framework. It does not use any database and stores all the necessary data in the filesystem.
pyctures is published under the BOLA (Public Domain), so you can run the software anywhere, and do whatever you want with it.
Installation:
The installation procedure depends on the HTTP server youre using. What follows is a list of procedures for some common HTTP servers. If you use pyctures with something else, please let me know so I can add it here.
After youve completed the install, read the "Administration" file to learn how to manage your gallery.
Common procedure
1. Copy the "website" directory to a suitable place where you want to install
pyctures. It does not have to be inside your website, but has to be
readable by your webservers user.
2. Create a "config.py" file based on the "config.py.sample" file, and edit it
according to your configuration. A really important setting is the album
path, where all albums will be stored. It can be anywhere you want. Create
an admin user so you can create albums using the web interface.
3. Make sure the album path is writeable by the user who will run the pyctures
application. It usually is your web server user.
4. Install PIL from http://www.pythonware.com/products/pil/. The package name
for most distributions is "python-imaging" or just "imaging".
5. Install cheetah from http://www.cheetahtemplate.org/. The package name for
most distributions is "python-cheetah" or just "cheetah". You need at least
version 2.0-rc5.
No server (stand-alone)
pyctures can be run without any HTTP server by just executing
"./pyctures [PORT]" directly on the website directory. Its useful for
testing and small sites. I recommend that you test everything works this way
before integrating it into a webserver.
lighttpd
First of all, install "flup", from http://www.saddi.com/software/flup/.
Gentoo: Its not in portage, it sucks. Check
http://bugs.gentoo.org/show_bug.cgi?id=100784
Debian: apt-get install python-flup
Now, lets suppose youve installed pyctures in the "/var/www/pyctures"
directory, and want to publish it under the "/pics/" directory.
You need to add the following to /etc/lighttpd/mod_fastcgi.conf (or just
/etc/lighttpd/lighttpd.conf if you dont have the other file):
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
fastcgi.server = (
"/pics" => ((
"socket" => "/tmp/fastcgi-pics.socket",
"max-procs" => 1,
"bin-path" => "/var/www/pyctures/pyctures"
))
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
This is enough, but be aware that "http://mysite/pics" (note the missing
"/" at the end) will *not* be redirected to pyctures.
If you want to be able to refer to your pyctures root both as
"http://mysite/pics/" and "http://mysite/pics", you need to add the
following in the same file as before:
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
url.redirect = (
"^/pics$" => "/pics/"
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
And then create an empty file in your document root called "gallery",
otherwise lighttpd will think the path does not exist and return 404 before
doing the redirection.
Enhancements:
- This version implemented pagination, IE support, and automatic thumbnail regeneration on config changes.
- It also improved performance considerably, reduced the memory footprint, added Apache installation instructions, and included several other minor improvements.

COCANWIKI provides a full-featured Wiki and content management system.
It has many unique features not found in any other Wikis including live preview when editing, advanced navigation (including the ability to follow links in both directions), PIM/calendar extensions, user permissions, customisable page layouts, virtual hosting (handling more than one Wiki per server), search, anti-spam, and email notifications.
Main features:
- Interactive preview
- Powerful markup
- Per-section editing
- Editing help
- Detects conflicts during concurrent editing
- Support for Unicode (non-Western character sets)
- Customisable page layout
- Stylesheets
- CSS id for sections
- Full user management
- Permissions
- Email notification
- Virtual hosting
- Image upload
- Mail import
- Calendar
- Navigation
- Search from 404 page
- Sitemap
- Anti-spam
- Email notification
- Contact forms
- Site menu
- Themes
- RSS feeds from pages
- Per-page feedback form
- Mailing list management
- Highlights terms from search engines

Mobile Web Proxy is a (CGI) tool to make more Web pages available from some mobile devices (cell phone Web browsers, etc.).
When I began using my cell phones mobile web browser, one of the things I realized was that there were a lot of web pages that my cell phones web browser simply wouldnt let me see. My shiny new Motorola Razr from T-Mobile, for many pages, would display an error message like "413: Page cannot be displayed." It happened annoyingly often; browsing the web from my cell phone was a lot like trying to read a book or a magazine with large chunks simply ripped out. And when I tried troubleshooting, I might have missed something, but it seemed like a big problem without an easily available solution.
So I tried to provide my own solution. I made a proxy that would present webpages for the mobile web so that they would display in a way that would work for my cell phones web browser. Technologies include paging, tag cleaning, and optional caching to improve performance, but without getting into technical details, this means that I can access some pages on the web that I couldnt access earlier.
Enhancements:
- A bug that caused the script to spuriously report 404 errors was fixed.
- A smaller default page size was set so that tag-rich pages would be rendered in a way more likely to be displayable on mobile Web browsers.