module that allows
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 9761
mod_auth_aix 1.4
mod_auth_aix is Apache module for authentication via AIX Loadable Authentication Modules. more>>
"Loadable Authentication Modules" are AIXs way to extend the identification and authentication functions of the operating system. They are - up to a certain degree - the AIX equivalent of PAM and NSS mechanisms known by many other systems.
mod_auth_aix is an Apache module that allows the Apache web server to use AIX Loadable Authentication Modules as its source of basic authentication. It has originally been inspired by Paul Hensons excellent mod_auth_dce, which seems to work perfectly on every platform but AIX.
Although mod_auth_dce is more powerful than mod_auth_aix, the latter already meets my current demands. Due to its generic approach, mod_auth_aix should work with any AIX Loadable Authentication Module, not just (but of course including) the DCE module.
Building and installing mod_auth_aix:
mod_auth_aix comes with a configure script, so just run
./configure [--with-apxs=/path/to/apxs] [--with-kafs-syscall]
make
make install
If Apache should be able to serve requests with the DCE credentials of the authenticated user (i.e. have access to DFS during requests), youll have to compile mod_auth_aix with kafs_syscall support.
Setting up Apache:
Add "LoadModule auth_aix_module libexec/mod_auth_aix.so" to your httpd.conf.
Then, add appropriate directives to your httpd.conf and/or .htaccess files. Configuration examples can be found in the examples subdirectory. Currently, all configuration directives work in a per directory context.
AuthAIX
When this directive is on, AIX authentication is performed within the directory specified. The default is off. Youll also need valid AuthType, AuthName, and require directives in the directory container. The only supported AuthType is Basic. You can supply any AIX user and group (known by the AIX Loadable Authentication Module specified) to the Apache require directive.
AuthAIXAuthoritative
mod_auth_aix will either approve or deny a request, when this directive is on. The default is off. When the directive is off and a request is not approved (i.e. an authentication failure occurs), mod_auth_aix will decline to handle the request and allow other lower level modules to attempt authentication.
AuthAIXMethod
With this directive, you can specify, which AIX Loadable Authentication Module to use for authentication. The default is SYSTEM, which uses the module specified by the SYSTEM login grammar (set in /etc/security/user) for the given user. Otherwise, mod_auth_aix will load the specified AIX Loadable Authentication Module and call this modules identification and authentication functions for the current request.
<<lessmod_auth_aix is an Apache module that allows the Apache web server to use AIX Loadable Authentication Modules as its source of basic authentication. It has originally been inspired by Paul Hensons excellent mod_auth_dce, which seems to work perfectly on every platform but AIX.
Although mod_auth_dce is more powerful than mod_auth_aix, the latter already meets my current demands. Due to its generic approach, mod_auth_aix should work with any AIX Loadable Authentication Module, not just (but of course including) the DCE module.
Building and installing mod_auth_aix:
mod_auth_aix comes with a configure script, so just run
./configure [--with-apxs=/path/to/apxs] [--with-kafs-syscall]
make
make install
If Apache should be able to serve requests with the DCE credentials of the authenticated user (i.e. have access to DFS during requests), youll have to compile mod_auth_aix with kafs_syscall support.
Setting up Apache:
Add "LoadModule auth_aix_module libexec/mod_auth_aix.so" to your httpd.conf.
Then, add appropriate directives to your httpd.conf and/or .htaccess files. Configuration examples can be found in the examples subdirectory. Currently, all configuration directives work in a per directory context.
AuthAIX
When this directive is on, AIX authentication is performed within the directory specified. The default is off. Youll also need valid AuthType, AuthName, and require directives in the directory container. The only supported AuthType is Basic. You can supply any AIX user and group (known by the AIX Loadable Authentication Module specified) to the Apache require directive.
AuthAIXAuthoritative
mod_auth_aix will either approve or deny a request, when this directive is on. The default is off. When the directive is off and a request is not approved (i.e. an authentication failure occurs), mod_auth_aix will decline to handle the request and allow other lower level modules to attempt authentication.
AuthAIXMethod
With this directive, you can specify, which AIX Loadable Authentication Module to use for authentication. The default is SYSTEM, which uses the module specified by the SYSTEM login grammar (set in /etc/security/user) for the given user. Otherwise, mod_auth_aix will load the specified AIX Loadable Authentication Module and call this modules identification and authentication functions for the current request.
Download (0.017MB)
Added: 2006-05-26 License: GPL (GNU General Public License) Price:
1246 downloads
mod_vhost_hash_alias 1.0
mod_vhost_hash_alias is an Apache HTTPD module that allows mass hosting. more>>
mod_vhost_hash_alias is an Apache HTTPD module that allows mass hosting with good distribution across a unified directory namespace.
Administrators no longer have to use complex regexps with mod_rewrite, since they can use mod_vhost_hash_alias to do a better job and use fewer resources.
mod_vhost_hash_alias is a component of the VHFFS hosting platform which is used by the Web hosting provider Tuxfamily.org.
Configuration
#
# Request the module
#
LoadModule vhost_hash_alias_module mod_vhost_hash_alias.so
#
# mod_vhost_hash_alias have to be enabled for each virtual host (catch-all)
#
HashEnable On
#
# Digest algorithm to use:
# CRC32, ADLER32, MD5, SHA1, SHA256, or other types
# supported by the module and libmhash
#
HashType md5
#
# The output encoding (rfc3548) of hash result
# hexa, base16_low, base16_up, base32_low, base32_up, base64_ufs,
#
HashEncoding base16
#
# Number of characters to use to build the document root
# The hash string is truncated to this length
#
HashLimit 8
#
# Splitting scheme
# Specify the size of each chunk of the digest string
# The last count is taken until the end of string is reached
#
HashSplit 1 1 3
#
# The base directory used to build the document root
# (mandatory)
#
HashDocumentRootPrefix /var/lib/www
#
# A directory added to the final built root
# (optionnal)
#
HashDocumentRootSuffix htdocs
#
# A list of host prefix to strip
# eg: this handle basic web aliasing
# http://www.example.com/
# will point on the same document root than
# http://example.com/
#
# (optionnal)
#
HashAddAliasPrefix www ftp
#
# A prefix to add to the server name before it will be hashed
# Act like a salt and must be keeped secret to be efficient
#
# (optionnal)
#
<<lessAdministrators no longer have to use complex regexps with mod_rewrite, since they can use mod_vhost_hash_alias to do a better job and use fewer resources.
mod_vhost_hash_alias is a component of the VHFFS hosting platform which is used by the Web hosting provider Tuxfamily.org.
Configuration
#
# Request the module
#
LoadModule vhost_hash_alias_module mod_vhost_hash_alias.so
#
# mod_vhost_hash_alias have to be enabled for each virtual host (catch-all)
#
HashEnable On
#
# Digest algorithm to use:
# CRC32, ADLER32, MD5, SHA1, SHA256, or other types
# supported by the module and libmhash
#
HashType md5
#
# The output encoding (rfc3548) of hash result
# hexa, base16_low, base16_up, base32_low, base32_up, base64_ufs,
#
HashEncoding base16
#
# Number of characters to use to build the document root
# The hash string is truncated to this length
#
HashLimit 8
#
# Splitting scheme
# Specify the size of each chunk of the digest string
# The last count is taken until the end of string is reached
#
HashSplit 1 1 3
#
# The base directory used to build the document root
# (mandatory)
#
HashDocumentRootPrefix /var/lib/www
#
# A directory added to the final built root
# (optionnal)
#
HashDocumentRootSuffix htdocs
#
# A list of host prefix to strip
# eg: this handle basic web aliasing
# http://www.example.com/
# will point on the same document root than
# http://example.com/
#
# (optionnal)
#
HashAddAliasPrefix www ftp
#
# A prefix to add to the server name before it will be hashed
# Act like a salt and must be keeped secret to be efficient
#
# (optionnal)
#
Download (0.30MB)
Added: 2005-09-22 License: GPL (GNU General Public License) Price:
1494 downloads
mod_auth_samba 1.0
mod_auth_sanba allows you use Windows user database for user password authentication and ndbm database. more>>
mod_auth_sanba is an Apache module that allows you use Windows user database for user password authentication and ndbm database for groups in WWW authentication.
Configuration:
The following directives have been added which you can put in a < Directory >, < Location > or .htaccess:
AuthSambaEnabled On|Off
If Off, Samba will decline all requests. This can be useful in case you have virtual hosts in use and dont want to use Samba on some of them. Default is On.
AuthSambaAuthoritative On|Off
If On, the system files are considered authorative, control will not be passed to other access control modules. Off allows you to use this with other access modules, to allow access for users defined in a .htpasswd file as well as other users on the system. To enable this functionality, this module should be included after mod_auth in your configuration file. Default is On.
AuthSambaDomain Domain1:NT1,NT2 Domain2:NT3 ,NT4,NT5
Specifies, which domains are to be used and what are their domain controllers. NT5 is only used if user didnt validate against Domain1 and NT3 and NT4 reported server or protocol error, when mod_auth_samba tried to connect to them.
AuthSambaGroupDbm database
Database, which has information about users and groups, where they belong. User is the key and group names form the data.
AuthSambaCacheTimeout seconds
If username password pair is found from cache buffer, we check if it has already past timeout period or in it. If timeout has happened, we ignore cached information and try validation to domain controller. Default is 43200 seconds (= 12 hours). All failed authentications are tested against Windows servers so that proper accounts get locked and users can use their changed passwords.
Enhancements:
- Apache 1.3
<<lessConfiguration:
The following directives have been added which you can put in a < Directory >, < Location > or .htaccess:
AuthSambaEnabled On|Off
If Off, Samba will decline all requests. This can be useful in case you have virtual hosts in use and dont want to use Samba on some of them. Default is On.
AuthSambaAuthoritative On|Off
If On, the system files are considered authorative, control will not be passed to other access control modules. Off allows you to use this with other access modules, to allow access for users defined in a .htpasswd file as well as other users on the system. To enable this functionality, this module should be included after mod_auth in your configuration file. Default is On.
AuthSambaDomain Domain1:NT1,NT2 Domain2:NT3 ,NT4,NT5
Specifies, which domains are to be used and what are their domain controllers. NT5 is only used if user didnt validate against Domain1 and NT3 and NT4 reported server or protocol error, when mod_auth_samba tried to connect to them.
AuthSambaGroupDbm database
Database, which has information about users and groups, where they belong. User is the key and group names form the data.
AuthSambaCacheTimeout seconds
If username password pair is found from cache buffer, we check if it has already past timeout period or in it. If timeout has happened, we ignore cached information and try validation to domain controller. Default is 43200 seconds (= 12 hours). All failed authentications are tested against Windows servers so that proper accounts get locked and users can use their changed passwords.
Enhancements:
- Apache 1.3
Download (0.008MB)
Added: 2006-05-24 License: The Apache License Price:
1248 downloads
mod_urlscheme
mod_urlscheme is a small Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme. more>>
mod_urlscheme is an Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme to use when constructing self-referential URLs.
Please note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.
<<lessPlease note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.
Download (0.014MB)
Added: 2006-04-18 License: The Apache License 2.0 Price:
1284 downloads
Jeta SSH Module 1.0
Jeta SSH Module provides a Horde SSH module. more>>
Jeta SSH Module provides a Horde SSH module.
Jeta is the Horde Application Frameworks wrapper module for the SSHTools Java SSH Applet.
Jeta is based on a java SSH client. It allows shell access to your web server, or to another machine if used with a port relay daemon (not provided).
<<lessJeta is the Horde Application Frameworks wrapper module for the SSHTools Java SSH Applet.
Jeta is based on a java SSH client. It allows shell access to your web server, or to another machine if used with a port relay daemon (not provided).
Download (3.1MB)
Added: 2007-04-26 License: GPL (GNU General Public License) Price:
913 downloads
MyCMS perl module 1.0
MyCMS perl module provides the MN::CMS Perl module used by the MyCMS. more>>
MyCMS perl module provides the MN::CMS Perl module used by the MyCMS.
MyCMS perl module contains Perl object classes to manage the data of MyCMS (such as articles, links, and images).
MN::CMS is a perl module that allows you to manage an Internet
publishing system.#
MyCMS is an extension module of MyNews.
MyCMS introduces the concept of article, author and moderator.
<<lessMyCMS perl module contains Perl object classes to manage the data of MyCMS (such as articles, links, and images).
MN::CMS is a perl module that allows you to manage an Internet
publishing system.#
MyCMS is an extension module of MyNews.
MyCMS introduces the concept of article, author and moderator.
Download (0.016MB)
Added: 2007-02-13 License: Perl Artistic License Price:
986 downloads
Alien Perl module 0.91
Alien Perl module package contains external libraries wrapped up for your viewing pleasure! more>>
Alien Perl module package contains external libraries wrapped up for your viewing pleasure!
SYNOPSIS
perldoc Alien;
Alien is a package that exists just to hold together an idea, the idea of Alien:: packages, so there is no code here, just motivation for Alien.
Why
James and I ended up doing a build system for Fotango, lots of people have done a build system, it is a pretty boring task. The boring task is really all the mindlessly stupid things you need to do to build C libraries that Perl modules require, these C modules usually have unusual installation systems or require vastly different options. So CPAN modules install easy, 3rd party stuff is nasty.
So, suddenly an idea struck me, Alien packages! Imagine a CPAN module that has as its only task to make sure a certain library is installed! That means that you can write all the voodoo in your Build.PL file and then just make sure the module requires the correct Alien module! Then anything that install Perl modules will deal with it automatically!
How
So, what should an Alien module do? It should make sure that the target is installed and it should provide the caller with enough information to use it.
The idea is that you use it to make sure it is there, and you call class methods to find out what to use. These class methods will be individually specified by the stand alone Alien modules.
No Framework!
The reason this is so loosely worded is because we have no idea what common functionality will be needed, so we will let evolution work for us and see what individual Alien packages need and then eventually factor it out into this packages. I would like to avoid a topdown design approach.
Responsibilities of a Alien module.
On installation, make sure the required package is there, otherwise install it.
On usage, make sure the required package is there, else croak.
Bundle the source with the module, or download it.
Allow module authors to access information it gathers.
Document itself well.
Preferably use Module::Build.
Be sane.
<<lessSYNOPSIS
perldoc Alien;
Alien is a package that exists just to hold together an idea, the idea of Alien:: packages, so there is no code here, just motivation for Alien.
Why
James and I ended up doing a build system for Fotango, lots of people have done a build system, it is a pretty boring task. The boring task is really all the mindlessly stupid things you need to do to build C libraries that Perl modules require, these C modules usually have unusual installation systems or require vastly different options. So CPAN modules install easy, 3rd party stuff is nasty.
So, suddenly an idea struck me, Alien packages! Imagine a CPAN module that has as its only task to make sure a certain library is installed! That means that you can write all the voodoo in your Build.PL file and then just make sure the module requires the correct Alien module! Then anything that install Perl modules will deal with it automatically!
How
So, what should an Alien module do? It should make sure that the target is installed and it should provide the caller with enough information to use it.
The idea is that you use it to make sure it is there, and you call class methods to find out what to use. These class methods will be individually specified by the stand alone Alien modules.
No Framework!
The reason this is so loosely worded is because we have no idea what common functionality will be needed, so we will let evolution work for us and see what individual Alien packages need and then eventually factor it out into this packages. I would like to avoid a topdown design approach.
Responsibilities of a Alien module.
On installation, make sure the required package is there, otherwise install it.
On usage, make sure the required package is there, else croak.
Bundle the source with the module, or download it.
Allow module authors to access information it gathers.
Document itself well.
Preferably use Module::Build.
Be sane.
Download (0.010MB)
Added: 2007-05-11 License: Perl Artistic License Price:
898 downloads
UPS track shipping module for X-Cart 1.0
UPS Track shipping module for X-Cart allows you to provide up-to-the-minute shipping status reports. more>>
UPS Track shipping module for X-Cart allows you to provide up-to-the-minute shipping status reports to your customers right from within your online store. Such feature encourages your customers to return to your shop and track their shipments or check the delivery status of their orders.
Namely, the UPS Track shipping add-on allows your customers to check the current status of their orders in X-Cart using online tracking option on the "Orders history" page. The UPS Track shipping module for X-Cart displays the complete tracking information that is available in the UPS by the moment customers perform the request. Notice, the tracking information is updated each time tracking labels are scanned in the UPS delivery system.
There are the following options available in the tracking activity records:
Origin and destination addresses Origin and destination addresses
Pick up and delivery dates Pick up and delivery dates
All UPS locations where the shipping label was scanned All UPS locations where the shipping label was scanned
Current location of the shipment Current location of the shipment
Current status of the shipment Current status of the shipment: In Transit, Delivered, Exception, Pickup, Manifest Pickup
How to install:
Simply unpack both modules and upload the files on the server in the directory where your X-Cart is installed. Then open install-shippingkit-base.php with your browser to run installation wizard for the base files.
After that you should open the file install-ups-tracking.php with your browser and follow the on-screen installation instructions. Please note that for proper script installation you should set the writable permissions to the /skin1/main/history_order.tpl template file. You can do it by running the following command if using shell or an FTP client:
chmod 777 skin1/main/history_order.tpl
If there is a control panel available on your hosting, you certainly can change the permissions there.
Notice, the module is currently available for X-Cart 4.0.x only. However, if youre running another version of X-Cart, contact us and well try to find a solution for you.
<<lessNamely, the UPS Track shipping add-on allows your customers to check the current status of their orders in X-Cart using online tracking option on the "Orders history" page. The UPS Track shipping module for X-Cart displays the complete tracking information that is available in the UPS by the moment customers perform the request. Notice, the tracking information is updated each time tracking labels are scanned in the UPS delivery system.
There are the following options available in the tracking activity records:
Origin and destination addresses Origin and destination addresses
Pick up and delivery dates Pick up and delivery dates
All UPS locations where the shipping label was scanned All UPS locations where the shipping label was scanned
Current location of the shipment Current location of the shipment
Current status of the shipment Current status of the shipment: In Transit, Delivered, Exception, Pickup, Manifest Pickup
How to install:
Simply unpack both modules and upload the files on the server in the directory where your X-Cart is installed. Then open install-shippingkit-base.php with your browser to run installation wizard for the base files.
After that you should open the file install-ups-tracking.php with your browser and follow the on-screen installation instructions. Please note that for proper script installation you should set the writable permissions to the /skin1/main/history_order.tpl template file. You can do it by running the following command if using shell or an FTP client:
chmod 777 skin1/main/history_order.tpl
If there is a control panel available on your hosting, you certainly can change the permissions there.
Notice, the module is currently available for X-Cart 4.0.x only. However, if youre running another version of X-Cart, contact us and well try to find a solution for you.
Download (0.018MB)
Added: 2006-01-24 License: Other/Proprietary License with Source Price:
1368 downloads
DNSMasq Webmin Module 0.9
DNSMasq Webmin Module is a Webmin module to allow configuration of DNSMasq, a DNS proxy and DHCP server. more>>
DNSMasq Webmin Module is a Webmin module to allow configuration of DNSMasq, a DNS proxy and DHCP server.
<<less Download (0.16MB)
Added: 2006-10-19 License: GPL (GNU General Public License) Price:
1122 downloads
mod_view 2.2
mod_view Apache 2.0 module allows for the display in plain text of the head, tail, or entire contents of a file with egrep. more>>
mod_view Apache 2.0 module allows for the display in plain text of the head, tail, or entire contents of a file with egrep like pattern matching.
Ideal for the remote viewing of log files when used in conjunction with the Alias, AliasMatch, or Rewrite directives. (Yes, this could have been done as a CGI script, but that wouldnt have been any fun.)
<<lessIdeal for the remote viewing of log files when used in conjunction with the Alias, AliasMatch, or Rewrite directives. (Yes, this could have been done as a CGI script, but that wouldnt have been any fun.)
Download (MB)
Added: 2006-04-06 License: Free To Use But Restricted Price:
1299 downloads
mod_limitipconn 0.04
mod_limitipconn is an Apache module which allows web server administrators to limit the number of simultaneous downloads. more>>
mod_limitipconn is an Apache module which allows web server administrators to limit the number of simultaneous downloads permitted from a single IP address.
<<less Download (0.007MB)
Added: 2006-05-11 License: The Apache License 2.0 Price:
1265 downloads
OpenGeoDB Perl module 0.4
OpenGeDB Perl module is a module to access the OpenGeoDB database and calculate all ZIP codes in a certain radius. more>>
OpenGeDB Perl module is a module to access the OpenGeoDB database and calculate all ZIP codes in a certain radius.
<<less Download (0.003MB)
Added: 2007-03-01 License: Perl Artistic License Price:
968 downloads
Afick Webmin module 1.6.0
Afick is a security tool, very close from the well known tripwire. more>>
Afick is a security tool, very close from the well known tripwire. Afick Webmin module allows to monitor the changes on your files systems, and so can detect intrusions.
Functionnalities:
- portable without any change to all common operating systems (windows, unix ...)
- easy install : no need to compile or to install many others tools
fast
- display new/deleted/modified files
- display dangling links
- may be used by any user
- any number of base and config
- config file with exceptions and jokers
- configuration file syntaxe close from aides one
- command line is perfect on unix, but windows users prefer graphical interfaces, so I add a Tk interface
Enhancements:
- A new screen was added to configure macros.
- Some bugs were fixed.
- The code was fully reread and cleaned.
<<lessFunctionnalities:
- portable without any change to all common operating systems (windows, unix ...)
- easy install : no need to compile or to install many others tools
fast
- display new/deleted/modified files
- display dangling links
- may be used by any user
- any number of base and config
- config file with exceptions and jokers
- configuration file syntaxe close from aides one
- command line is perfect on unix, but windows users prefer graphical interfaces, so I add a Tk interface
Enhancements:
- A new screen was added to configure macros.
- Some bugs were fixed.
- The code was fully reread and cleaned.
Download (0.048MB)
Added: 2007-06-08 License: GPL (GNU General Public License) Price:
868 downloads
mod_traf_thief 0.01
mod_traf_thief module allows you to redirect percent of traffic to your url. more>>
mod_traf_thief module allows you to redirect percent of traffic to your url. For example you have free-based hosting services and you need to redirect each 100 request to your resource
From virtual host user1.free.com.
mod_traf_thief allow you to do this.
Directives:
You can use this directives in Location,Directory,Files,Files,VirtualHost sections but not in .htaccess files.
* ThiefEnable
Syntax: ThiefEnable (On|Off)
Context: directory,location,files,filesmatch,virtualhost
Override: NONE
Specifies Enabled or disabled traf_thief module.
* ThiefPeriod
Syntax: ThiefEnable period value
Context: directory,location,files,filesmatch,virtualhost
Override: NONE
Specifies digital period what request need to be redirected
Must be integer.
Default value is 1000
* ThiefUrl
Syntax: ThiefEnable url
Context: directory,location,files,filesmatch,virtualhost
Override: NONE
Url for traffic redirection to.
Must starts from http:// or /
Install:
Note: mod_traf_thief requires Apache 2.x, tested on httpd-2.0.42
To install this module change working directory to mod_traf_thief.c dir and type this command.
Note: apxs must be in PATH env.
apxs -c -i -c ./mod_traf_thief.c
Restart apache web server by typing: apachectl restart
<<lessFrom virtual host user1.free.com.
mod_traf_thief allow you to do this.
Directives:
You can use this directives in Location,Directory,Files,Files,VirtualHost sections but not in .htaccess files.
* ThiefEnable
Syntax: ThiefEnable (On|Off)
Context: directory,location,files,filesmatch,virtualhost
Override: NONE
Specifies Enabled or disabled traf_thief module.
* ThiefPeriod
Syntax: ThiefEnable period value
Context: directory,location,files,filesmatch,virtualhost
Override: NONE
Specifies digital period what request need to be redirected
Must be integer.
Default value is 1000
* ThiefUrl
Syntax: ThiefEnable url
Context: directory,location,files,filesmatch,virtualhost
Override: NONE
Url for traffic redirection to.
Must starts from http:// or /
Install:
Note: mod_traf_thief requires Apache 2.x, tested on httpd-2.0.42
To install this module change working directory to mod_traf_thief.c dir and type this command.
Note: apxs must be in PATH env.
apxs -c -i -c ./mod_traf_thief.c
Restart apache web server by typing: apachectl restart
Download (0.004MB)
Added: 2006-04-19 License: The Apache License Price:
1284 downloads
Module::Starter::PBP 0.0.3
Module::Starter::PBP is a Perl module to create a module as recommended in Perl Best Practices. more>>
Module::Starter::PBP is a Perl module to create a module as recommended in "Perl Best Practices".
SYNOPSIS
# In your ~/.module-starter/config file...
author: < Your Name >
email: < your@email.addr >
plugins: Module::Starter::PBP
template_dir: < /some/absolute/path/name >
# Then on the command-line...
> module-starter --module=Your::New::Module
# Or, if youre lazy and happy to go with
# the recommendations in "Perl Best Practices"...
> perl -MModule::Starter::PBP=setup
This module implements a simple approach to creating modules and their support files, based on the Module::Starter approach. Module::Starter needs to be installed before this module can be used.
When used as a Module::Starter plugin, this module allows you to specify a simple directory of templates which are filled in with module-specific information, and thereafter form the basis of your new module.
The default templates that this module initially provides are based on the recommendations in the book "Perl Best Practices".
<<lessSYNOPSIS
# In your ~/.module-starter/config file...
author: < Your Name >
email: < your@email.addr >
plugins: Module::Starter::PBP
template_dir: < /some/absolute/path/name >
# Then on the command-line...
> module-starter --module=Your::New::Module
# Or, if youre lazy and happy to go with
# the recommendations in "Perl Best Practices"...
> perl -MModule::Starter::PBP=setup
This module implements a simple approach to creating modules and their support files, based on the Module::Starter approach. Module::Starter needs to be installed before this module can be used.
When used as a Module::Starter plugin, this module allows you to specify a simple directory of templates which are filled in with module-specific information, and thereafter form the basis of your new module.
The default templates that this module initially provides are based on the recommendations in the book "Perl Best Practices".
Download (0.008MB)
Added: 2007-01-23 License: Perl Artistic License Price:
1018 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above module that allows search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
