Date: 11/14/07     Keywords: apache

Anyone here in Atlanta at ApacheCon?

Look for the guy in black with the pipe in one hand and a book in the other. That's me.

Source: http://community.livejournal.com/apache/39386.html

Date: 11/14/07     Keywords: apache

Anyone here in Atlanta at ApacheCon?

Look for the guy in black with the pipe in one hand and a book in the other. That's me.

Source: http://apache.livejournal.com/39386.html

Date: 11/14/07     Keywords: apache

Anyone here in Atlanta at ApacheCon?

Look for the guy in black with the pipe in one hand and a book in the other. That's me.

Source: https://apache.livejournal.com/39386.html

Date: 10/29/07     Keywords: apache

I'm running my Apache 2 install on a Windows system. It seems that using a colon causes a 403 (Forbidden) error. I figured this is because it thinks the colon is pretending to be a drive label (thingy thing).

Anyway, how'd I fix that? Is there a way?

Source: http://community.livejournal.com/apache/38945.html

Date: 09/11/07     Keywords: apache

Our project is interested in buying a solid analytics application for several sites hosted on an Apache server.   What are our best options?

Source: http://community.livejournal.com/apache/38750.html

Date: 09/11/07     Keywords: apache

Our project is interested in buying a solid analytics application for several sites hosted on an Apache server.   What are our best options?

Source: http://apache.livejournal.com/38750.html

Date: 09/11/07     Keywords: apache

Our project is interested in buying a solid analytics application for several sites hosted on an Apache server.   What are our best options?

Source: https://apache.livejournal.com/38750.html

Date: 08/27/07     Keywords: php, apache

I want to generate links with my code like "index_flotsam.php" and "index_jetsam.php" and have apache ignore everything but "index.php". So if the user clicks on "index_flotsam.php" it will just take them to the file "index.php" but will still display the url "index_flotsam.php". I'm using Apache 2.2.4. I have a feeling I could probably do this with the FilesMatch directive, but I'm not entirely sure how. Any ideas?

Thanks!

Source: http://community.livejournal.com/apache/38566.html

Date: 08/27/07     Keywords: php, apache

I want to generate links with my code like "index_flotsam.php" and "index_jetsam.php" and have apache ignore everything but "index.php". So if the user clicks on "index_flotsam.php" it will just take them to the file "index.php" but will still display the url "index_flotsam.php". I'm using Apache 2.2.4. I have a feeling I could probably do this with the FilesMatch directive, but I'm not entirely sure how. Any ideas?

Thanks!

Source: http://apache.livejournal.com/38566.html

Date: 08/27/07     Keywords: php, apache

I want to generate links with my code like "index_flotsam.php" and "index_jetsam.php" and have apache ignore everything but "index.php". So if the user clicks on "index_flotsam.php" it will just take them to the file "index.php" but will still display the url "index_flotsam.php". I'm using Apache 2.2.4. I have a feeling I could probably do this with the FilesMatch directive, but I'm not entirely sure how. Any ideas?

Thanks!

Source: https://apache.livejournal.com/38566.html

Date: 06/28/07     Keywords: browser, apache

We bought a certificate for a domain.   I've set up a few sites with ssl before this, so I was careful to enter the FQDN in my csr request.  A day later Verisign sent the cert in an email, which we copied into a sitename.crt file on the server.   I made an unecrypted version of the key so I wouldn't have to enter the passphrase every time Apache starts.  (yes I entered the passphrase, which was accepted)

So - I start the server without errors.  When I access the site using https://sitename, the browser returns a certificate mismatch error.   The cert details appear with localhost, localdomain, ect, which is not what I entered when creating the csr & key. 


    ServerName sitename.department.domain.ext
    ServerAdmin abc@123.def
    DocumentRoot /www/virtualhosts/sitename
    ErrorLog /var/log/httpd/sitename-error_log
    CustomLog /var/log/httpd/sitename-access_log common
    SSLEngine On
    SSLCertificateFile /usr/local/ssl/crt/sitename.crt
    SSLCertificateKeyFile /usr/local/ssl/crt/sitename_unencrypted.key
    SSLCACertificateFile /usr/local/ssl/crt/intermediate.crt



Is there a way to print out the details listed in a crt file, from command line?   Can I do the same with the original csr file?  

Source: http://community.livejournal.com/apache/38398.html

Date: 06/28/07     Keywords: browser, apache

We bought a certificate for a domain.   I've set up a few sites with ssl before this, so I was careful to enter the FQDN in my csr request.  A day later Verisign sent the cert in an email, which we copied into a sitename.crt file on the server.   I made an unecrypted version of the key so I wouldn't have to enter the passphrase every time Apache starts.  (yes I entered the passphrase, which was accepted)

So - I start the server without errors.  When I access the site using https://sitename, the browser returns a certificate mismatch error.   The cert details appear with localhost, localdomain, ect, which is not what I entered when creating the csr & key. 


    ServerName sitename.department.domain.ext
    ServerAdmin abc@123.def
    DocumentRoot /www/virtualhosts/sitename
    ErrorLog /var/log/httpd/sitename-error_log
    CustomLog /var/log/httpd/sitename-access_log common
    SSLEngine On
    SSLCertificateFile /usr/local/ssl/crt/sitename.crt
    SSLCertificateKeyFile /usr/local/ssl/crt/sitename_unencrypted.key
    SSLCACertificateFile /usr/local/ssl/crt/intermediate.crt



Is there a way to print out the details listed in a crt file, from command line?   Can I do the same with the original csr file?  

Source: http://apache.livejournal.com/38398.html

Date: 06/28/07     Keywords: browser, apache

We bought a certificate for a domain.   I've set up a few sites with ssl before this, so I was careful to enter the FQDN in my csr request.  A day later Verisign sent the cert in an email, which we copied into a sitename.crt file on the server.   I made an unecrypted version of the key so I wouldn't have to enter the passphrase every time Apache starts.  (yes I entered the passphrase, which was accepted)

So - I start the server without errors.  When I access the site using https://sitename, the browser returns a certificate mismatch error.   The cert details appear with localhost, localdomain, ect, which is not what I entered when creating the csr & key. 


    ServerName sitename.department.domain.ext
    ServerAdmin abc@123.def
    DocumentRoot /www/virtualhosts/sitename
    ErrorLog /var/log/httpd/sitename-error_log
    CustomLog /var/log/httpd/sitename-access_log common
    SSLEngine On
    SSLCertificateFile /usr/local/ssl/crt/sitename.crt
    SSLCertificateKeyFile /usr/local/ssl/crt/sitename_unencrypted.key
    SSLCACertificateFile /usr/local/ssl/crt/intermediate.crt



Is there a way to print out the details listed in a crt file, from command line?   Can I do the same with the original csr file?  

Source: https://apache.livejournal.com/38398.html

Date: 06/21/07     Keywords: apache

I guess lots of people (including me) are having problems getting Apache to work on Vista. I don't know if anyone's already posted this solution, but I pieced it together from a few different sites that each offered their own little tidbit. I hope this helps someone:

1) if you have already been trying to make this work, make sure you completely remove and detele all evidence of apache 2.2.4 from your computer: program files, registry, etc. if you haven't had a failed install attempt and you're starting fresh, go on to step 2.
2) turn off User Access Control
2) run cmd.exe as an administrator. you can do this by right-clicking on the link in the start menu program list.
3) from the command line, go to the directory your apache msi file is in. enter: "msiexec /i .msi" (without the quotes obviously)
5) let the program run, check off everything as you see fit. when the program has finished running, it will most likely display an error popup. close this.
6) back on the command line (still running as administrator), go to \bin and enter: "httpd -k install"
7) now apache should show up as a service. but you're not done yet! go to the apache monitor/control thingy in your start menu. right-click it and go to properties->compatibility. set the compatibility mode to winxp sp2.
8) that's it! you may want to start your apache control, but it will run now without that.

Source: http://community.livejournal.com/apache/37811.html

Date: 06/21/07     Keywords: apache

I guess lots of people (including me) are having problems getting Apache to work on Vista. I don't know if anyone's already posted this solution, but I pieced it together from a few different sites that each offered their own little tidbit. I hope this helps someone:

1) if you have already been trying to make this work, make sure you completely remove and detele all evidence of apache 2.2.4 from your computer: program files, registry, etc. if you haven't had a failed install attempt and you're starting fresh, go on to step 2.
2) turn off User Access Control
2) run cmd.exe as an administrator. you can do this by right-clicking on the link in the start menu program list.
3) from the command line, go to the directory your apache msi file is in. enter: "msiexec /i .msi" (without the quotes obviously)
5) let the program run, check off everything as you see fit. when the program has finished running, it will most likely display an error popup. close this.
6) back on the command line (still running as administrator), go to \bin and enter: "httpd -k install"
7) now apache should show up as a service. but you're not done yet! go to the apache monitor/control thingy in your start menu. right-click it and go to properties->compatibility. set the compatibility mode to winxp sp2.
8) that's it! you may want to start your apache control, but it will run now without that.

Source: http://apache.livejournal.com/37811.html

Date: 06/21/07     Keywords: apache

I guess lots of people (including me) are having problems getting Apache to work on Vista. I don't know if anyone's already posted this solution, but I pieced it together from a few different sites that each offered their own little tidbit. I hope this helps someone:

1) if you have already been trying to make this work, make sure you completely remove and detele all evidence of apache 2.2.4 from your computer: program files, registry, etc. if you haven't had a failed install attempt and you're starting fresh, go on to step 2.
2) turn off User Access Control
2) run cmd.exe as an administrator. you can do this by right-clicking on the link in the start menu program list.
3) from the command line, go to the directory your apache msi file is in. enter: "msiexec /i .msi" (without the quotes obviously)
5) let the program run, check off everything as you see fit. when the program has finished running, it will most likely display an error popup. close this.
6) back on the command line (still running as administrator), go to \bin and enter: "httpd -k install"
7) now apache should show up as a service. but you're not done yet! go to the apache monitor/control thingy in your start menu. right-click it and go to properties->compatibility. set the compatibility mode to winxp sp2.
8) that's it! you may want to start your apache control, but it will run now without that.

Source: https://apache.livejournal.com/37811.html

Date: 06/13/07     Keywords: no keywords

Hi guys!!!

wts24h is starting a series of the art competitions!
Here is the first competition!

"Open Letter to Bill Gates".

The best short story will be awarded  100$  in PayPal.
The winner will be chosen by the greatest number of votes.
You can post your short stories here for 7 days,
and then we start voting :-)


pic from Freaking News.com

Source: http://community.livejournal.com/apache/37388.html

Date: 06/12/07     Keywords: no keywords

I created two name-based virtual hosts

NameVirtualHost *:80


ServerName siteone.subX.subY.com
ServerAdmin me@me.com
DocumentRoot /www/virtualhosts/siteone
ErrorLog /var/log/httpd/siteone-error_log
CustomLog /var/log/httpd/siteone-access_log common



ServerName sitetwo.subX.subY.com
ServerAdmin me@me.com
DocumentRoot /www/virtualhosts/sitetwo
ErrorLog /var/log/httpd/sitetwo-error_log
CustomLog /var/log/httpd/sitetwo-access_log common

Source: http://community.livejournal.com/apache/37226.html

Date: 06/12/07     Keywords: no keywords

I created two name-based virtual hosts

NameVirtualHost *:80


ServerName siteone.subX.subY.com
ServerAdmin me@me.com
DocumentRoot /www/virtualhosts/siteone
ErrorLog /var/log/httpd/siteone-error_log
CustomLog /var/log/httpd/siteone-access_log common



ServerName sitetwo.subX.subY.com
ServerAdmin me@me.com
DocumentRoot /www/virtualhosts/sitetwo
ErrorLog /var/log/httpd/sitetwo-error_log
CustomLog /var/log/httpd/sitetwo-access_log common

Source: http://apache.livejournal.com/37226.html

Date: 06/12/07     Keywords: no keywords

I created two name-based virtual hosts

NameVirtualHost *:80


ServerName siteone.subX.subY.com
ServerAdmin me@me.com
DocumentRoot /www/virtualhosts/siteone
ErrorLog /var/log/httpd/siteone-error_log
CustomLog /var/log/httpd/siteone-access_log common



ServerName sitetwo.subX.subY.com
ServerAdmin me@me.com
DocumentRoot /www/virtualhosts/sitetwo
ErrorLog /var/log/httpd/sitetwo-error_log
CustomLog /var/log/httpd/sitetwo-access_log common

Source: https://apache.livejournal.com/37226.html