Re: [PATCH] build problem with stable and older libtool
This has been in the STATUS file a while anyway. That makes 3 +1s, since there was already my vote: * get out-of-tree APR builds to work for libtool 1.3.x users buildconf: r1.32 +1: trawick (Note that the diff is different from r1.32 with APACHE_2_0_BRANCH since the code has to be added to APACHE_2_0_BRANCH instead of modified. The only difference was the comment... I kept the comment the same as in HEAD so that APACHE_2_0_BRANCH doesn't have unique code.) William A. Rowe, Jr. wrote: I'll see your +1 and raise you +1... I thought the patch was required to build with apr out of tree - if everyone is going to be bit on libtool 1.3 releases let's get it in there now, and into the .45 release. Bill At 06:16 PM 3/24/2003, Greg Ames wrote: I'm trying to get WROWE_2_0_45_RC1 going on daedalus and got: /home/gregames/httpd-2.0.45-wr1/shlibtool: /home/gregames/httpd-2.0.45-wr1/shlibtool: No such file or directory *** Error code 127 ...when make tried to build mod_access (the first module we build as a DSO). This is a symptom of using libtool 1.3 without having ltconfig and ltmain.sh accessable to httpd's configure. Looks like we need 1.29 and 1.31 in the tag. That's what this patch does, in addition to tweaking the comment a little to make it more obvious why this code is important. This patch solves the problem. Can I get some +1's on committing it to the stable branch? Thanks, Greg Index: buildconf
Re: AIX: ld -bI:httpd.exp vs. ld -lhttpd
Stas Bekman wrote: Yesterday, I've patched the mod_perl 2.0 build code to build on aix (tested on powerpc/aix/5.1). The interesting thing that I haven't used .exp's at all (neither -lapr/-laprutil/etc). I've used -berok and -brtl and let everything to be resolved at the startup time. This seems to work just fine, since by the time mod_perl boots, httpd/apr/aprutil are all loaded in memory. Do you think this will work on other aix versions/platforms? I think so (at least 4.3 and above) you do have run-time linking enabled, right? using the APR ldflags (like apxs does) will get that turned on
RE: mod_disk_cache problem
Hi Harry,
I did set mod_expires to set an expiry date of access plus 1 week -
and when I GET the urls from the site I see the correct Expires:
value in the header-
Yet mod_disk_cache won't cache any dynamic content (perl scripts, tomcat
jsp's, etc).
It does cache all the static content that apache fetches from the disk,
though.
Any idea why would that happen?
Thanks,
Ori.
-Original Message-
From: harald deppeler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 6:32 PM
To: Ori Tend
Cc: [EMAIL PROTECTED]
Subject: Re: mod_disk_cache problem
Hi Ori
On Wed, Mar 19, 2003 at 04:14:45PM +0200, Ori Tend wrote:
Hi again Harry,
Just wanted to let you know you've helped me :-)
It really was the case- I chown-ed the cache directory to user nobody,
and apached started to fill it with some files... I assumed that it
should be the same owner as the owner of the other apache log files..
I assumed wrong :-)
Glad this helped. I remember bumping into this as well ...
I have another question, though- it looks like apache doesn't cache
the dynamic info that tomcat generates (tomcat is connected via
mod_jk). Any idea why? I also tried to enable mod_proxy, but it didn't
help- tomcat still receives the same requests again and again, even
though apache is supposed to cache it...
The way I understand it:
mod_cache caches according to the HTTP RFC, which means that the
back-end ought to provide appropriate headers that help the cache
determine how long it should cache the data. If the backend does not
provide any such headers (expire, last-modified), the cache doesn't
cache, especially if the URL contains a query string.
At work I recently ran into a similar problem. (Pseudo-) dynamic
back-end content with no such cache-friendly headers *had* to be cached
(or our site would performance crash) and we modified a 2.0.44 vanilla
Apache to serve our needs. Since most changes are a rather quick hack
and since they violate the RFC, I did not dare to propose them to the
list but feel free to use them (they should be attached to this mail).
You would patch like
#!/bin/sh -ex
DIRECTORY=httpd-2.0.44
files_to_patch=mod_cache.c mod_disk_cache.c
path_to_files=${DIRECTORY}/modules/experimental
for file in $files_to_patch
do
patch ${path_to_files}/$file ${file}.diff
done
exit 0
before doing the make to compile.
The patch also enables that URLs ending with a / are cached.
Cheers - Harry
Thanks,
Ori.
-Original Message-
From: Ori Tend [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 16, 2003 8:03 PM
To: 'harald deppeler'
Subject: RE: mod_disk_cache problem
Hi Harry,
First off, thanks for your reply :-)
/usr/local/apache2/proxy owned by root- and I run apache always as
root (also, all of apache's other directories are owned by root, so I
assume this is ok for apache).
I tried to play with the CacheDefaultExpire, hoping that is the reason
why apache didn't write anything to the CacheRoot directory, but it
didn't help- apache doesn't write anything to that directory...
I kind of suspect it has to do with a compilation option I didn't set
or so... But I really don't know which...
Ori.
-Original Message-
From: harald deppeler [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 16, 2003 7:10 PM
To: Ori Tend
Subject: Re: mod_disk_cache problem
On Sun, Mar 16, 2003 at 04:03:35PM +0200, Ori Tend wrote:
I'm using apache standard cache configuration (loading
mod_disk_cache). Yet for some reason, apache doesn't write anything
to
the CacheRoot dir. Just to make sure I didn't do anything wrong, I
reinstalled apache
again- this time on Win32, and using
the exact same cache configuration apache cached all the urls, as it
should have.
Just to make sure it doesn't have to do with mod_jk2 and tomcat
connectivity, I tried to see if apache caches static content (html
files which are not served by tomcat) - and apache didn't cache
those
as well.
any help would be greatly appreciated...
my httpd.conf (all is default, commented in the following):
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
CacheRoot /usr/local/apache2/proxy
CacheSize 5
CacheGcInterval 4
CacheMaxExpire 24
CacheLastModifiedFactor 0.1
CacheDefaultExpire 1
CacheEnable disk /
Is /usr/local/apache2/proxy writable by the httpd UID?
Does your backend service generate HTTP headers that set the caching
expiry time? If not, your default expiry time would be 1 second. Is
that really what you want?
If any of this helps, please post the solution to the list.
Cheers - Harry
Re: [PATCH] build problem with stable and older libtool
Jeff Trawick wrote: This has been in the STATUS file a while anyway. That makes 3 +1s, since there was already my vote: ooops, I should have looked there first. From the commit logs it appeared that there might have been a misunderstanding about what was essential and what was a nice new feature. Greg
Re: Testers; Apache 2.0 release candidate is tagged
William A. Rowe, Jr. wrote: Apache 2.0 testers, can you please help move forward the next HTTPD release by checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag? This should look something like; WROWE_2_0_45_RC1 looks good for me on Unix (prefork, worker MPMs on Linux and AIX)
Re: Testers; Apache 2.0 release candidate is tagged
Greg Ames wrote: can you please help move forward the next HTTPD release by checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag? I'm done testing and happy with it on daedalus, with the patch to buildconf of course. I intend to bounce the production server over to this build later today, once the load goes down. Greg
Re: cvs commit: httpd-2.0/modules/arch/win32 mod_win32.c
From: William A. Rowe, Jr. Doesn't the Apache on Windows web server have available a built-in Windows Scripting Engine and two built-in scripting languages, that do not use the # as a scripting comment marker? No; Windows has a command-line Windows Scripting Host (cscript, as opposed to the window-based wscript). quote The Windows Scripting Engine serves as the component within Windows that interprets and executes script code written in scripting languages such as JScript or VBScript. /quote This Windows Scripting Engine component is used by many types of hosts: Windows Script Host - (WSH 5.6) has two parts. Cscript.exe - CUI - command line (like Perl.exe) Accesses COM and file system, StdIn, StdErr and StdOut for usage as say admin config type scripts or for accessing LDAP or ADSI or WMI or databases or Regex and etc. (lots more) on the desktop or server to server. Could run in Apache on Windows web server. Wscript.exe - GUI - output in window boxes on the screen much like those in the MsgBox. Same usage as Cscript.exe above but with different output. Best for desktop usage for admin type config usage same as Cscript.exe above but with the different output way (MsgBox style). Should not be used in Apache on Windows. Http Applications - HTA - Html files that run on the desktop but not via the browser. Uses a separate DLL. Accesses some COM and file system like WSH but is not the Windows Script Host. Desktop and server or to server. Could run on as Intranet usage with Apache on Windows. Not for the Internet. Internet Explorer - Browser usage. Internet - limits on Com and file system. Desktop - used for displays of list boxes, radio and combo boxes with WSH scripts. OS - Used in the Windows OS. No need here to explain DLLs usage. ASP - Used in IIS. (Sort of, but close enough for here without explaining all the DLLs used by everything.) Programs - Windows and third party programs. Calls the Com access to the engine and the scripting language usage is available. So the Windows Script Host is one of many ways that the Apache on Windows web server have available a built-in Windows Scripting Engine and two built-in scripting languages, that do not use the # as a scripting comment marker. There are a lot of add-in (downloadable) languages for usage with the Windows Scripting Engine. But there are only two built-in languages, VBScript and JScript. As André indicated, this is most trivially enabled using the Registry-based ScriptInterpreterSource directives. It is actually recommended that you use ScriptInterpreterSource registry-strict which will invoke the ExecCGI verb, instead of using the Open verb. Since it is most trivially enabled using the Registry-based ScriptInterpreterSource directives then why is this not the default (unneeded to turn on) for _all_ Apache on Windows? This ScriptInterpreterSource default would allow usage of the built-in Windows Scripting Engine as well as any other Windows OS known programs, such as Perl. There would be no need for _any_ scripting comment marker checking routine with the Apache on Windows web server. But if any scripting comment marker checking routine (of the shebang type), is performed, on Apache on Windows, without first having the ScriptInterpreterSource as the default, then this component within Windows that is available to every Apache on Windows web server, the built-in Windows Scripting Engine and it's built-in default languages, should be included into this scripting comment marker checking routine first, if not at least, somewhere in the #! checking routine in Apache on Windows. But if it is compat ways one seeks, then have the Unix type Apache versions, only check for ' (a single quote) and then the Unix type versions of Apache, can run two files also! :) This patch is a no-op relative to VB/J Scripts. But one added a BOM change (so changes are allowed) and yet left the #!, that is not used with Windows Scripting Engine's built-in default languages, available in all Apache on Windows web servers. There are many scripting languages, so if any scripting comment marker checking routine is needed, on Apache on Windows, then an option for scripting languages is needed too. A lot is happening with the Windows Scripting Engine. And most people only use it properly with the other Windows
Re: Testers; Apache 2.0 release candidate is tagged
William A. Rowe, Jr. schrieb: Apache 2.0 testers, can you please help move forward the next HTTPD release by checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag? This should look something like; Hello I did the RC1 build for win32. So far it looks good, rotatelogs/pipe logs seems to work again. But one thing with SSL causes me troubles. The SSLMutex always creates this message in the error log on the first access with a HTTPS request: [Tue Mar 25 21:04:55 2003] [warn] (OS 123)Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch. : Cannot reinit SSLMutex Sorry, I have a german OS, but the meaning of the message is: Syntax for the filename, directoryname or volumename is wrong. I actually have SSLMutex left on the default setting of ssl.conf, which looks: # Semaphore: # Configure the path to the mutual exclusion semaphore the # SSL engine uses internally for inter-process synchronization. SSLMutex file:logs/ssl_mutex Even trying to specify a full path/filename with / and \ didn't help to resolve this message. According to the changes.txt there where modifications in the SSLMutex stuff in the 2.0.45 changes. Any ideas ? André
Re: Testers; Apache 2.0 release candidate is tagged
At 02:20 PM 3/25/2003, André Schild wrote: William A. Rowe, Jr. schrieb: Apache 2.0 testers, can you please help move forward the next HTTPD release by checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag? The SSLMutex always creates this message in the error log on the first access with a HTTPS request: [Tue Mar 25 21:04:55 2003] [warn] (OS 123)Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch. : Cannot reinit SSLMutex I got the message from it's number (thank goodness we finally group these by 'role') - and I'm diagnosing now. Bill
daedus is running httpd-2.0.45-dev
...since Tuesday, 25-Mar-2003 13:56:10 PST. It looks fine so far. Please let us know if you notice anything odd. This is the WROWE_2_0_45_RC1 tag from yesterday with a patch to buildconf. Greg
Re: Testers; Apache 2.0 release candidate is tagged
William A. Rowe, Jr. schrieb: At 02:20 PM 3/25/2003, André Schild wrote: William A. Rowe, Jr. schrieb: Apache 2.0 testers, can you please help move forward the next HTTPD release by checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag? The SSLMutex always creates this message in the error log on the first access with a HTTPS request: [Tue Mar 25 21:04:55 2003] [warn] (OS 123)Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch. : Cannot reinit SSLMutex I got the message from it's number (thank goodness we finally group these by 'role') - and I'm diagnosing now. There is a small error in my previous mail. Of course I use the SSLMutex default config entry, as on win32 you only have the choice between none and default. I'm using openssl 0.9.7a and MS dev studio 6.0 André
Re: Removing Server: header
On Saturday, March 22, 2003, at 07:15 AM, Brass, Phil (ISS Atlanta) wrote: The point of stripping Date and Last-modified headers is that HTTP fingerprinting tools look at things like header order, the formatting of dates and times, etc. So change the format and order. Stripping them is a protocol violation. Alternately, does anybody know why the Server, Date, Accept-Ranges, Last-Modified, and other headers are put in last, after things like mod_headers run? Perhaps a better patch would be to move the code that adds these headers to the respose earlier in the code so that users can simply use mod_headers to strip whichever ones they want, or a module for randomizing header order could be written, etc. They are put in last specifically to prevent them from being randomized by buggy modules. Roy
Re: AIX: ld -bI:httpd.exp vs. ld -lhttpd
Jeff Trawick wrote: Stas Bekman wrote: Yesterday, I've patched the mod_perl 2.0 build code to build on aix (tested on powerpc/aix/5.1). The interesting thing that I haven't used .exp's at all (neither -lapr/-laprutil/etc). I've used -berok and -brtl and let everything to be resolved at the startup time. This seems to work just fine, since by the time mod_perl boots, httpd/apr/aprutil are all loaded in memory. Do you think this will work on other aix versions/platforms? I think so (at least 4.3 and above) so far it seems to work with 4.3 and 5.1 you do have run-time linking enabled, right? using the APR ldflags (like apxs does) will get that turned on Yup, -brtl __ Stas BekmanJAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide --- http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
Hi, question about external module.
Hi, I got a problem when I'm working on adding an externalmodule as a filter of Apache 2.0. Please help me to figure out the solution. I'mbuilding an external module to embed a C/C++ like scripting language, CH,executing for Apache 2.0 server. I studied from php module source programand got the simulated idea to build this module. I use pre_config,post_config and post_read_request hooks. Ideally when Apache server startup,the pre_config hook is executed and the post_read_request hook should beused when requesting the target file type, for example, *.php. And thenexecute the script by activating module for that type, eg. mod_php. I builtmy own module and it works in Ret Hat Linux 7.x. However, when I port thismodule (mod_ch) to Windows 2000, Apache server seems can not reach the"post_read_request" hook. (I print out message at every hook function) I used thesame configuration setup as to Linux version, except the directory paths.I'm thinking is there any special setup needed for W2K to enable thepost_read_request hook? Does anybody have someexperience to build a module as a filter in Apache 2.0 server + Windows 2000? Please helpme to figure out the problem. I appreciate your any help.Best Regards,Jeffrey Huang
