Low-Latency Access on Trillions of Records:
Technically the answer is yes, Apache supports that method. However it does not come with any scripts or programs which actually implement the publishing behaviour. This article explains what the PUT method is, how it can be used in Apache, and what is required to support publishing with it.
It also gives a basic script to handle publishing, and explains why this script should be used very carefully to prevent security problems. First published giving write access to apache Apache Week issue 59 4th April This is the standard way to get back information from a server.
The information itself may come from a static page, a CGI program, a server-side include page or any other source handled by the server. By definition it is safe for a browser to obtain a page by GET as many times as it likes - it will never cause any permanent action on the server such as entering a product order.
To perform a permanent action on the server, the "POST" method is used.
This method must be handled by a program or script, and the browser should not re-request a POST page without getting the user to confirm it. This POST method is used when a script or program requires a lot of form data input or when the request makes the server perform a real action such as entering an order.
The difference is that the POST method is normally handed a script which is explicitly named by the resource that is, something that already existswhile a PUT request could be directed at a resource which does not yet exist.
Another difference is that the POST method can be used in response to a form, while the PUT method can only contain a single data item. The PUT method is suited for publishing pages. There is some confusion about whether Apache supports the PUT method.
That is, it supports it, but in order for it to do anything useful you need to supply a suitable CGI program. This is done with the Script directive.
This specifies a script i. Note that you also need to make sure that this script is executable, by either placing it in a ScriptAlias directory, or giving it a suitable extension and turning on CGI execution for that extension. The CGI script has to be able to accept a page sent it, and look and the request URL to decide where to place the file.
If it is successful it should return a status of or if everything went ok. The basic operation of a PUT script should be: A simplistic script to implement PUT handling like this is available in put1. Among aother limitations, this script does not check to see if you are attempting to upload a CGI script or if the destination is a directory.
However the main failing is that it implements no security checks, and if you have a secure setup it will not even have permission to update the files. The Security Isssues Configuring Apache is the easy part: Some of the main security requirements are: Make sure the PUT script can only be run by authorised users Make sure that the script can update only web content files Make sure the authorised users can only update their pages, not other people's pages on the same server The first issue can be addressed by making sure that the script is protected by username and password authentication.
The second issue is more complex. To be able to update the files on your server the script must have enough permission to write or create the content files.
This in itself is a security risk, since it means if a bug or security hole is found in any of your other CGI programs anyone on the Internet could potentially change any of your files. On most servers the httpd process runs a some relatively unprivileged user, such as "nobody".
This user should not own or have write access to any of the files on the server. So the first problem with generating a secure PUT script is determining how the script can get permissions to update files owned by a different user. One way of doing this, new in Apache 1. This allows a script to be run as a different user.
This comes with Apache but is not installed by default, because of the security risks it can create if used inappropriately.
You need to install it, and arrange it so that the PUT script is executed as the user that owns your web files. In this case, it would be sensible to ensure that this user does not have write access to any other parts of the file system, such as your Apache configuration files or.
The final security issue applies if you have multiple content providers such as different customers where you cannot trust them not to try to update each other's pages. There are several ways to add fix this: If the customers are in different virtual hosts, use the suEXEC mechanism to give each customer a different Unix username and execute the script as that user.
Use a different PUT script for each customer, with individual access authentication for each user, and hard-code the paths that they are allowed to update into the script. Assuming you have a PUT script which provides a level of security you are happy with, this section explains how to use these programs to publish pages.The O'Reilly Network has teamed with Red Hat Apache Week, the leading commercial Apache site to offer comprehensive Apache information and resources.
Apache Week offers news, feature articles, reviews, resources, and documentation. How can I give write-access of a folder to all users in linux?
I can just sudo everything but I would rather just give it write access.
How can I do this? I tried sudo chmod /var/www but it didn't work. linux permissions apache-http-server. share +1 for guid to force apache permissions. works well with umask of Note. The examples assume that mod_fcgid and other necessary modules are loaded into the server already, either built-in or via the LoadModule directive..
Additionally, the example configurations provide full access to the applications using access control directives which work with Apache and On computer file systems, different files and directories have permissions that specify who and what can read, write, modify and access them.
This is important because WordPress may need access to write to files in your wp-content directory to enable certain functions.. Permission Modes. A practical guide to secure and harden Apache Web Server. 1. Introduction. The Web Server is a crucial part of web-based applications.
Apache Web Server is often placed at the edge of the network hence it becomes one of the most vulnerable services to attack. The Apache Modules Book: Application Development with Apache and millions of other books are available for Amazon Kindle.