If you are using a recent version of the Apache server, then your Webmaster must give you "AllowOverride FileInfo" permission. Then you can put a file called .htaccess in any directory. (Note that in MIME terminology, "encoding" means "compression". In the XML encoding header, "encoding" means "coded character set") Here are some lines that may be useful-- Why do you want to send XML with the MIME type application/xml rather than text/xml? Because then the file will not be transcoded.

This question is often phrased as: I receive the "Internal Server Error" message (in the browser), and the following in the server log (/var/log/apache/error.log): Thu Apr 15 13:35:51 2004] [error] [client XX.XX.XX.XX] malformed header from script. Bad header=HTTP/1.

Test your posback script :: RTS Tutorial :: Request RTS Activation ::This article will help you Understand HTTP HEADERS we send with our REAL TIME STATISTICS (later on, RTS).

When a client connects to Apache, part of the information returned in the headers is the name "Apache" Additional information that can be sent is the version number, such as "1.3.26", the operating system, and a list of non-standard modules you have installed. Frequently, people want to remove this information, under the mistaken understanding that this will make the system more secure.

The libwww-perl bundle (LWP) is a collection of modules for WWW access in Perl. LWP is available from CPAN in source form, or you can install it using the Perl Package Manager (PPM). LWP may also be included with future binary releases of Perl. Aldo Calpini has developed a Perl for Win32 extension to do FTP and HTTP using the WININET library. It's in alpha testing and is available on his web page at http://www.divinf.it/dada/perl/

Author: Joshua Lynch (http://www.jguru.com/guru/viewbio.jsp?EID=103303) Question originally posed by Mike Reedy (http://www.jguru.com/guru/viewbio.jsp?EID=98127 I recently did this with Apache and Tomcat. Using Basic HTTP Authentication is an Apache function, so this method should work with Apache and any servlet engine. Different web servers will, of course, work differently. If you haven't already done so, read the Apache FAQ about authentication (section G) at apache.org, especially QA G.2.

The easiest way to fetch files using HTTP is to use the java.net.URL class. The openStream() method will return an InputStream instance, from which the file contents can be read. For added control, you can use the openConnection() method, which will return a URLConnection object. Here's a brief example that demonstrates the use of the java.net.URL.openStream() method to return the contents of a URL specified as a command line parameter. import java.net.*; import java.io.

One way to do this is by using a URLConnection to open a stream to your desired URL, then copy the data out of the stream to a file on your local file system. Use the standard java.net.URL class, or "roll your own" using java.net.Socket. Note: The servlet cannot initiate this connection! If the servlet needs to asynchronously send a message to the applet, then you must open up a persistent socket using java.net.Socket (on the applet side), and java.net.

To see what the Expires and Last-Modified headers are, open the page with Netscape and select 'page info' from the View menu. This will give you a menu of the page and any objects (like images) associated with it, along with their details. To see the full headers of an object, you'll need to manually connect to the Web server using a Telnet client. Depending on what program you use, you may need to type the port into a separate field, or you may need to connect to www.myhost.com:80 or www.

Apache does not automatically send a cookie on every response, unless you have re-compiled it with the mod_usertrack module, and specifically enabled it with the CookieTracking directive. This module has been in Apache since version 1.2. This module may help track users, and uses cookies to do this. If you are not using the data generated by mod_usertrack, do not compile it into Apache.

Even though the registered MIME type for MIDI files is audio/midi, some browsers are not set up to recognize it as such; instead, they look for audio/x-midi. There are two things you can do to address this: Configure your browser to treat documents of type audio/midi correctly. This is the type that Apache sends by default. This may not be workable, however, if you have many client installations to change, or if some or many of the clients are not under your control.

In general, you want your 'netmail' and 'netnews' parameters in static to result in valid headers, so that people can reply to you. If you can do so, get into a domain and domainize all your headers. It'll make your life easier and will do the same for people who exchange mail with you. The important thing to remember is that if you put a domain-style address out without being domainized, people will probably not be able to reply to your mail.

You can right click on a nickname on the nick list or notify list, select dcc, and then select send. That will bring up the file select dialog. Select the file to send and your file transfer begins.

In Unix (and therefore also on Mac OS X) files and folders that have names beginning with '.' are considered invisible. These are not shown by default, but you can temporarily display them by selecting Toggle Hidden Files from the Listing menu. This option temporarily switches the settings in the Preferences which govern invisible file display. In the Interface tab of the Preferences there are checkboxes to set whether you prefer invisible items to be shown or not.

htaccess files are special files that allow you to customize apache on a per-directory basis. A good place to start learning about .htaccess is the official apache documentation:

runs on Windows NT/9x, Netware 5.x and above, OS/2, and most versions of Unix, as well as several other operating systems DBM databases for authentication allows you to easily set up password-protected pages with enormous numbers of authorized users, without bogging down the server. Customized responses to errors and problems Allows you to set up files, or even CGI scripts, which are returned by the server in response to errors and problems, e.g.