Re: [us...@httpd] a chain of proxy servers
Heck no. I got lucky that I'm not white, so I got in with affirmative action... Did you get hired because of the Americans with Disabilities Act? If so, that's cool too... I guess not being able to read is a disability... On Wed, Jul 28, 2010 at 9:40 AM, James Godrej wrote: > > > ------ > *From:* Vincent Jong > > *To:* users@httpd.apache.org > *Sent:* Wed, 28 July, 2010 10:01:36 PM > *Subject:* Re: [us...@httpd] a chain of proxy servers > > How the heck did you get hired on as a sysadmin? :-/ > > so do u think u shld have been hired ? > > -- AFM #998 If there's anything more important than my ego around, I want it caught and shot now...
Re: [us...@httpd] a chain of proxy servers
How the heck did you get hired on as a sysadmin? :-/ On Wed, Jul 28, 2010 at 9:29 AM, James Godrej wrote: > > However, do remember that the > official documentation is not meant to be read as a how-to, but rather > as a technical reference with simple examples for most sections. > > Frank. > > Whose grand pa will write that.Do u even understand the plight of sys > admin. > Who has a boss who wont listen to urshit excuses. > > > -- AFM #998 If there's anything more important than my ego around, I want it caught and shot now...
Re: [us...@httpd] a chain of proxy servers
Funny... I learned how to administer apache by reading the docs... So do you want to hear an opinion of someone that used apache for the first time reading the docs? You probably don't since I'm sure your insurance won't pay for another wahmbulance trip to butt hurt hospital. On Wed, Jul 28, 2010 at 9:06 AM, James Godrej wrote: > > There is nothing to laugh in it. > Support is how Open Source companies earn their money from. > If some where you get a document which makes life easy why would some one > pay the money to support. > > > More than 70% of documentations on internet is written by some vague person > calling themselves to be an expert. > You read that go through it step by step then you find at some step it > failed you Google and then you try another non sense blog or what ever > and lo Gah!!! you again failed.You thoroughly rubbed your shoulders read > the Guides tutorials and then you find that things are not working. > At least in a proprietary software you are assured that such hassles will > not be a part of your life. > Some one is there to take care and understand the plight of end user. > When some one tells that Documentation is not proper then people cry. > > > If you actually want to write a clear document then > ask some one who used Apache for the first time to read your document and > do step by step what is mentioned if they could do > your doc is good else its useless. > -- > *From:* Eric Covener > * > *Either there's a conspiracy or you're too lazy/stupid to read the > technical documentation. Thanks for the laugh! > > > > -- AFM #998 If there's anything more important than my ego around, I want it caught and shot now...
Re: [us...@httpd] Directory Indexes
assuming you're on 2.2, look into IndexOptions, IndexStyleSheet, AddIconByEncoding, AddIcon, AddIconByType, AddDescription On Mon, Jan 11, 2010 at 9:43 PM, Programmer In Training < p...@joseph-a-nagy-jr.us> wrote: > I've been out of the loop for a VERY long time (since around 1.3.12) so > please forgive me my ignorance. > > In 1.3.12 I used to know how to get the directory index to look like this: > > http://www.boycottamerica.us/relevant-files/ > > and not like the current default look (a bulleted list of directories > and files with no descriptive information at all) when running on > Windows (I have it installed for local testing purposes only). While > this isn't a great big huge issue, I do like the old default look so > much better. All options except DocumentRoot are at the default values > at install. > -- > PIT > > -- If there's anything more important than my ego around, I want it caught and shot now...
Re: [us...@httpd] Apache config
if you've restarted apache recently, apache 2.0.54 requires the use of startssl to start up apache. ie. [ /foo ]# apachectl startssl On Tue, Dec 22, 2009 at 8:23 PM, Devraj Mukherjee wrote: > Provide us some more information please. > > - What OS are you using? > - If Linux can you do something like a netstat --listen and see if 443 > is being used. > - Change in firewall configuration > > On Wed, Dec 23, 2009 at 12:15 PM, cpanon wrote: > > > > Hello > > I have a Apache2.054 system that was working perfectly with https for > months. I was able to see the specific secured page, it was loading my > certificate file, excellent. All of a sudden, with no change in the > configuration, really, it is no longer listening on 443. I have the log as > recently as yesterday with it starting up and showing listening on 443 and > 80. Now just listening on 80.. I updated the drivers on the nics, both > Intel Pro, rebooted, clicked my heels. Nothing. Has anyone had such a > drastic change with it still working over 80? I will change the NIC, but > done believe the problem could be that specific. All ideas welcomed. tia. > > > > -- > "The secret impresses no-one, the trick you use it for is everything" > - Alfred Borden (The Prestiege) > > - > The official User-To-User support forum of the Apache HTTP Server Project. > See http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > " from the digest: users-digest-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > -- If there's anything more important than my ego around, I want it caught and shot now...
Re: [EMAIL PROTECTED] Certificate Import into Apache 2.2.0
I'm not an expert in anyway regarding certs or openssl and I'm assuming you've compiled apache with ssl support and the cert you're talking about is a server cert, you could probably try to edit your httpd.conf and httpd-ssl.conf file. The httpd-ssl.conf file is located in conf/extra and you can add the path to your cert and/or key in there. In httpd.conf, you would uncomment the include line that deals with the httpd-ssl.conf file. The line to uncomment would be: Include conf/extra/httpd-ssl.conf If that doesn't work, you probably want to convert your .p7b cert to something like PEM format and edit those conf files to point to the PEM cert. Unfortunately, I don't know much about .pb7 format as the only formats I've dealt with are .p12 and .pem certs. Again, I'm assuming you're talking about a server cert and not a CA cert. Vincent J. On Sun, 18 Dec 2005 22:54:15 -0800, Wulf Kaiser <[EMAIL PROTECTED]> wrote: Dear All, I have a perhaps simple but nonetheless serious problem. I have build, installed and configured an Apache 2.2.0 under Solaris 9, and i have a valid certificate file in .p7b format from the DFN CA. But: How can i import this into Apache? T.i.A, yours Wulf Kaiser IT Services Web Development | Database Administration Webmaster www.mpimf-heidelberg.mpg.de Zentrale Hard- und Softwarebeschaffung Max-Planck-Institut für medizinische Forschung Jahnstrasse 29 69120 Heidelberg Fon +49 6221 486560 Fax +49 6221 486561 Mobil +49 172 6235901 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
Listing what I did below to apply the patch, so if I made a mistake applying it, someone can let me know. 1. downloaded the patch to /home/some-user/temp 2. copied source tarball to /home/some-user/temp and untarred it. 3. cd /home/some-user/temp/httpd-2.2.0/modules/http 4. patch -i /home/some-user/temp/http_request.c.patch http_request.c I then preceded to configure, make, make install. I started up the new apache and saw the "It works!" index page of DocumentRoot and then tried to access http://localhost/cgi-bin/test-cgi and the error page still renders in HTML markup. The patch didn't work, so I'll file a bug after my chiropracter appointment. Thanks for all the help. =) Vincent J. On Fri, 16 Dec 2005 07:17:26 -0800, Joshua Slive <[EMAIL PROTECTED]> wrote: On 12/16/05, Vincent Jong <[EMAIL PROTECTED]> wrote: I'm not understanding what you mean. This was a clean install of apache and after typing make install, I started up this install's apache. I didn't edit the httpd.conf file. All the ErrorDocument lines that are in httpd.conf are example lines that are commented out already. So what is happening is when a user tries to access some cgi script that isn't configured right, this user gets the 500 Internal Server Error page. The problem with this page is that it is displayed as HTML code. There's the additional line of another 500 Internal Server Error occurring when trying to use an ErrorDocument handling the error request. Since I've never, ever configured any kind of customized error documents, I wouldn't even begin to know where all this error document configuration is. I prefer to use apache's default configuration and error pages. (Well, before you were including a bunch of extra errordocuments in your config via the Include directives at the bottom, but anyway...) My appologies, you are correct. I have been able to recreate the problem. This may be the same as the following bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=36090 Try the patch at the bottom of that report. If that doesn't fix the problem, please file a new bug report. Joshua. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
Really, I didn't change anything. I: 1. Stopped httpd 2. Renamed the older install directory from /usr/local/Apache2.2.X to /usr/local/Apache2.2.X.old 3. Copied the httpd source tarball to my temp directory. 4. Untarred it and did a cd to the extracted directory. 5. ./configure --prefix=/usr/local/Apache2.2.X \ --enable-so --enable-mods-shared=all \ --enable-ssl --with-ssl 6. make 7. make install as root 8. /usr/local/Apach2.2.X/bin/apachectl start Accessed http://localhost/cgi-bin/test-cgi and the error page rendered in HTML code. I didn't make any changes whatsoever to this install's httpd.conf file. Thanks, Vincent J. On Fri, 16 Dec 2005 06:49:29 -0800, Joshua Slive <[EMAIL PROTECTED]> wrote: On 12/16/05, Vincent Jong <[EMAIL PROTECTED]> wrote: Well, I did a clean install of apache. I didn't change anything, started up apache without any httpd.conf configuration changes and tried to access http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed as markup with the added message of: Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Basically the same problem as before. This is the configure command used: ./configure --prefix=/usr/local/Apache2.2.X \ --enable-so --enable-mods-shared=all \ --enable-ssl --with-ssl You're probably still using your old config files. You may indeed have found a bug here, but I am very skeptical that you can trigger it without *any* changes to the default config (such as activating the multilingual error documents). Joshua. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
I'm not understanding what you mean. This was a clean install of apache and after typing make install, I started up this install's apache. I didn't edit the httpd.conf file. All the ErrorDocument lines that are in httpd.conf are example lines that are commented out already. So what is happening is when a user tries to access some cgi script that isn't configured right, this user gets the 500 Internal Server Error page. The problem with this page is that it is displayed as HTML code. There's the additional line of another 500 Internal Server Error occurring when trying to use an ErrorDocument handling the error request. Since I've never, ever configured any kind of customized error documents, I wouldn't even begin to know where all this error document configuration is. I prefer to use apache's default configuration and error pages. Thanks, Vincent J. On Fri, 16 Dec 2005 00:27:22 -0800, Octavian Rasnita <[EMAIL PROTECTED]> wrote: Hi, From: "Vincent Jong" <[EMAIL PROTECTED]> Well, I did a clean install of apache. I didn't change anything, started up apache without any httpd.conf configuration changes and tried to access http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed as markup with the added message of: Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Basically the same problem as before. Have you tried without that ErrorDocument line in httpd.conf? Does that line run another cgi script? If yes, has this script right permissions (chmod 755)? What do you mean when you say that instead of an error it prints an html response? Even when Apache prints an error in the header, it also prints a short html page in the body. Maybe conf/extra/httpd-multilang-errordoc.conf print a larger html content, and in that case some browsers will display that html content instead of creating its own error page based on the error code. Every response prints a response code. If you say that it prints just an html page instead of an error, this means that it prints another code than 500. Which is that code? Try with: telnet localhost 80 GET http://localhost/cgi-bin/test.cgi HTTP/1.0 Teddy - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
Well, I did a clean install of apache. I didn't change anything, started up apache without any httpd.conf configuration changes and tried to access http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed as markup with the added message of: Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Basically the same problem as before. This is the configure command used: ./configure --prefix=/usr/local/Apache2.2.X \ --enable-so --enable-mods-shared=all \ --enable-ssl --with-ssl Thanks, Vincent J. On Thu, 15 Dec 2005 17:10:58 -0800, Joshua Slive <[EMAIL PROTECTED]> wrote: On 12/15/05, Vincent Jong <[EMAIL PROTECTED]> wrote: 16. uncommented 'Include conf/extra/httpd-mpm.conf', 'Include conf/extra/httpd-multilang-errordoc.conf', 'Include conf/extra/httpd-autoindex.conf', 'Include conf/extra/httpd-languages.conf', and 'Include conf/extra/httpd-ssl.conf' lines - By default all the include lines were commented Well httpd-multilang-errordoc.conf is certainly important here. The problem will likely go away if you comment that out. There are a bunch of ErrorDocument directives in there. Most likely they are interacting poorly with some other access restriction that you have added. Or you are missing some module required by those settings. Joshua. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
I did set up 2 .htaccess directories in the document root, but I don't know why this would cause this issue I'm seeing. But again, I've also successfully reproduced the problem with the original httpd.conf files on 2 different machines, which makes this extremely wierd, since there aren't any .htaccess directories specified in the original httpd.conf. Things I've changed in my httpd.conf file: 1. admin email address 2. server name 3. user nobody 4. group eng 5. ServerTokens Full 6. ServerSignature On 7. Options in DocumentRoot's directive 8. added directive for .htaccess protected directory in DocumentRoot 9. added another directive for .htaccess protected directory in DocumentRoot 10. set up UserDir directories and added directives for user directories 11. in , added values to DirectoryIndex directive 12. in , uncommented 'AddEncoding x-compress .Z' and 'AddEncoding x-gzip .gz .tgz' lines 13. in , uncommented 'AddHandler cgi-script .cgi' line and added '.pl' and '.py' to that line 14. in , uncommented 'AddHandler type-map var', AddType text/html .shtml', and 'AddOutputFilter INCLUDES .shtml' lines 15. in , added 'AddHandler php5-script .php', 'AddType text/html .php', and 'AddType application/x-httpd-php-source .phps' lines 16. uncommented 'Include conf/extra/httpd-mpm.conf', 'Include conf/extra/httpd-multilang-errordoc.conf', 'Include conf/extra/httpd-autoindex.conf', 'Include conf/extra/httpd-languages.conf', and 'Include conf/extra/httpd-ssl.conf' lines - By default all the include lines were commented I've also made changes to the httpd-ssl.conf file - admin email address, server name, and directive for subversion. I'm really not sure where to go from here since I've been able to reproduce this on 2 different machines with both my altered httpd.conf and the original httpd.conf files and you are not able to reproduce this. Thanks, Vincent J. On Thu, 15 Dec 2005 16:16:37 -0800, Joshua Slive <[EMAIL PROTECTED]> wrote: On 12/15/05, Vincent Jong <[EMAIL PROTECTED]> wrote: I also just noticed when reading the rendered page more correctly: Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. I've looked in the error log and it doesn't look like anything is funny in there. [Thu Dec 15 15:00:59 2005] [notice] Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7a DAV/2 configured -- resuming normal operations [Thu Dec 15 15:01:01 2005] [error] [client 127.0.0.1] (13)Permission denied: exec of '/usr/local/Apache2.2.X/cgi-bin/test-cgi' failed [Thu Dec 15 15:01:01 2005] [error] [client 127.0.0.1] Premature end of script headers: test-cgi It looks like there's an error somewhere in the configuration file, but I haven't done any changes regarding error documents... I'm having a hard time believing this statement. Have you checked any config file that may be Include'd in httpd.conf or any .htaccess file? Joshua. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
I also just noticed when reading the rendered page more correctly: Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. I've looked in the error log and it doesn't look like anything is funny in there. [Thu Dec 15 15:00:59 2005] [notice] Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7a DAV/2 configured -- resuming normal operations [Thu Dec 15 15:01:01 2005] [error] [client 127.0.0.1] (13)Permission denied: exec of '/usr/local/Apache2.2.X/cgi-bin/test-cgi' failed [Thu Dec 15 15:01:01 2005] [error] [client 127.0.0.1] Premature end of script headers: test-cgi It looks like there's an error somewhere in the configuration file, but I haven't done any changes regarding error documents... Thanks, Vincent J. On Thu, 15 Dec 2005 14:59:38 -0800, Vincent Jong <[EMAIL PROTECTED]> wrote: Yeah. I did that already on my home system and the error page is still being displayed as markup. I just tried it on my server at work, which is also running version 2.2.0, and the same problem occurs when using either my altered httpd.conf or the original httpd.conf file. I'm basically, just accessing one of the default cgi-scripts in cgi-bin that has the permissions 644. The URL I'm trying out is http://localhost/cgi-bin/test-cgi. Thanks, Vincent J. On Thu, 15 Dec 2005 10:18:30 -0800, Joshua Slive <[EMAIL PROTECTED]> wrote: On 12/14/05, Vincent Jong <[EMAIL PROTECTED]> wrote: I've upgraded to Apache 2.2.0 for *nix and I've come across a wierd behavior dealing with the 500 error page - it's being displayed on the browser as html code. I have not done any configuration in regards to error documents and this was not happening on version 2.0.55 which also did not have any error document configuration. All other error pages are rendering normally (such as 400 errors, etc...). To make sure it wasn't some configuration I missed, I used the httpd.conf in the original directory and restarted apache and the problem still existed with the original httpd.conf file. I guess, my questions are, is this a known issue and is there a workaround for getting the 500 error document to render correctly? I was on the #apache IRC room and there wasn't much help for me there as I tried to get someone else to reconfirm this. The easiest way to see this, which I was doing, was to change the permissions of a script in cgi-bin to 644 and then try to access the script. I can't replicate this problem. Try using the default config file that comes with 2.2.0 and see if you can recreate it. Joshua. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
Yeah. I did that already on my home system and the error page is still being displayed as markup. I just tried it on my server at work, which is also running version 2.2.0, and the same problem occurs when using either my altered httpd.conf or the original httpd.conf file. I'm basically, just accessing one of the default cgi-scripts in cgi-bin that has the permissions 644. The URL I'm trying out is http://localhost/cgi-bin/test-cgi. Thanks, Vincent J. On Thu, 15 Dec 2005 10:18:30 -0800, Joshua Slive <[EMAIL PROTECTED]> wrote: On 12/14/05, Vincent Jong <[EMAIL PROTECTED]> wrote: I've upgraded to Apache 2.2.0 for *nix and I've come across a wierd behavior dealing with the 500 error page - it's being displayed on the browser as html code. I have not done any configuration in regards to error documents and this was not happening on version 2.0.55 which also did not have any error document configuration. All other error pages are rendering normally (such as 400 errors, etc...). To make sure it wasn't some configuration I missed, I used the httpd.conf in the original directory and restarted apache and the problem still existed with the original httpd.conf file. I guess, my questions are, is this a known issue and is there a workaround for getting the 500 error document to render correctly? I was on the #apache IRC room and there wasn't much help for me there as I tried to get someone else to reconfirm this. The easiest way to see this, which I was doing, was to change the permissions of a script in cgi-bin to 644 and then try to access the script. I can't replicate this problem. Try using the default config file that comes with 2.2.0 and see if you can recreate it. Joshua. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] 500 Internal Server Error pages being rendered as markup
I've upgraded to Apache 2.2.0 for *nix and I've come across a wierd behavior dealing with the 500 error page - it's being displayed on the browser as html code. I have not done any configuration in regards to error documents and this was not happening on version 2.0.55 which also did not have any error document configuration. All other error pages are rendering normally (such as 400 errors, etc...). To make sure it wasn't some configuration I missed, I used the httpd.conf in the original directory and restarted apache and the problem still existed with the original httpd.conf file. I guess, my questions are, is this a known issue and is there a workaround for getting the 500 error document to render correctly? I was on the #apache IRC room and there wasn't much help for me there as I tried to get someone else to reconfirm this. The easiest way to see this, which I was doing, was to change the permissions of a script in cgi-bin to 644 and then try to access the script. Thanks for your time in this matter. Vincent J. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
