None No options are allowed. Every one of
None No options are allowed. Every one of the nifty features discussed here will not work. SymLinksIfOwnerMatch The server will use symlinks if the owner of the symlink is the owner of the file that the symlink points to. This means, in English, that a user can use symlinks to point to her own documents. AllowOverride If you allow override, users can alter the options permitted in a directory. When you allow override, Apache checks each directory for a file called .htaccess, and processes the contents as additional server configuration info. This allows Web developers to both handle much routine configuration themselves and to install insecure CGI scripts in random locations. You’ll need to decide whether to permit the use of .htaccess overrides. If you’re running a corporate Web server, and your Web developer pretty much gets what he wants anyway, there’s no reason not to allow whatever override he desires. If, on the other hand, you’re running a public or ISP Web server, and you don’t allow a certain group of clients to use CGI scripts, you should be sure to disallow certain overrides. These are the valid AllowOverride statements; all allow the user to override anything with an .htaccess entry. AuthConfig allows you to password-protect directories. This is a pretty safe option, and it is generally expected on server farms where any idiot with a credit card can get an account. FileInfo allows users to insert their own MIME information for a directory. While it’s generally better to add this sort of information to the server’s mime.types file, there will be occasions where people need this for example, when they upload a file that’s used only within their company, and they need to tell the browsers what to expect. Indexes allows the user to control how indexing is handled, including setting a new default document, controlling how icons appear in server-generated indexes, and so on. Limit allows the user to use the Allow, Deny, and Order keywords. This option is also quite safe. None means that the user can make no changes. This is a good option to use as a default, but it’s a little too restrictive for most applications. Options allows the user to set any of the options described here. This is good if you know and trust the Web developers, or if you don’t care if someone uploads an insecure program and the server is compromised. With the foregoing in mind, a reasonable set of user defaults is ………………………………………………………………………………………. AllowOverride Limit, AuthConfig, Indexes, FileInfo ………………………………………………………………………………………. Controlling HTTP Requests An HTTP method is a command sent by a browser to a server. you’ve probably heard of the HTTP methods GET and POST. These tell the server to transmit a particular page and to process a list of uploaded information, respectively. There’s a whole list of methods, however, each with a separate 348
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost PHP Web Hosting services