How to leave a message for a certain user?
Apache HTTP Server
Hello Guest
  
  • Login
• Register…
• Start blog
  • Who, Where, When
• What is interesting here?
• Duels
  • Polls
• Avatars
• Interests
  • Cities and Countries
• Random blog
• Users search
  • Search
• Games
• Tests
• QAIX
  • Сообщества
• Talxy Chat
• Horoscope
• Online
 
Register!

QAIX > Apache HTTP ServerGo to page: « previous | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | next »

  Top users: 
  Recent blog posts: 
  They have birthday today: 
  Forums:   
  Discuss: 
  Recent forum topics: 
  Recent forum comments:
  Модератор:
Wednesday, 27 June 2007
help! Doug Crowe 19:43:29
 can someone provide a link to download a pre-compiled win32 binary of a
c compiler that will work with CPAN?

Doug

-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
For additional commands, e-mail: users-help@httpd.ap­ache.org


comment 492 answer | Add comment
Saturday, 23 June 2007
password protect Eric 16:53:00
 
/usr/local/apache/h­tdocs/thisdirectory

how do I password protect a directory such as the above?

apache 2.x

thanks
Eric


-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


comment 5 answers | Add comment
Thursday, 21 June 2007
Authentification problem with Apache 2.23 and OpenLDAP 2.2 on win32 Michel SANCHEZ 15:50:25
 Hi,

Apache 2.2.3, OpenLDAP 2.2.29, both on win32.

It seems that the LDAP authentification mechanism with mod_authnz_ldap.so doesn't work.

Apache configuration httpd conf :

LoadModule ldap_module modules/mod_ldap.so­
LoadModule authnz_ldap_module modules/mod_authnz_­ldap.so

ProxyPass / balancer://mycluste­r stickysession=jsess­ionid nofailover=on
<Location />
Order allow,deny
Allow from all
AuthType Basic
AuthName "Cluster Test"
AuthBasicProvider ldap
AuthzLDAPAuthoritat­ive off
AuthLDAPBindDN "cn=Manager,dc=my-d­omain,dc=com"
AuthLDAPBindPasswor­d "admin"

AuthLDAPURL "ldap://tola3000037­83.tls.fr.eu.airbus.­corp:389/ou=people,d­c=my-domain,dc=com?u­id"
Require valid-user
</Location>

The query with ldapsearch works well, from Apache i got en internal server error

Error log :
[Wed Jan 17 14:34:20 2007] [debug] mod_authnz_ldap.c(3­73): [client 152.3.74.202] [2184] auth_ldap authenticate: using URL ldap://tola30000378­3.tls.fr.eu.airbus.c­orp:389/ou=people,dc­=my-domain,dc=com?ui­d
[Wed Jan 17 14:34:20 2007] [warn] [client 152.3.74.202] [2184] auth_ldap authenticate: user michel authentication failed; URI / [ldap_search_ext_s() for user failed][Erreur de protocole]

slapd.log :
backend_startup: starting "dc=my-domain,dc=co­m"
bdb_db_open: dbenv_open(./data)
slapd starting
connection_get(1212­): got connid=0
connection_read(121­2): checking for input on id=0
ber_get_next
ber_get_next: tag 0x30 len 51 contents:
ber_get_next
do_bind
ber_get_next on fd 1212 failed errno=10035 (WSAEWOULDBLOCK)
ber_scanf fmt ({imt) ber:
ber_scanf fmt (m}) ber:>>> dnPrettyNormal: <cn=Manager,dc=my-d­omain,dc=com>
=> ldap_bv2dn(cn=Manag­er,dc=my-domain,dc=c­om,0)
ldap_err2string
<= ldap_bv2dn(cn=Manag­er,dc=my-domain,dc=c­om)=0 Success
=> ldap_dn2bv(272)
ldap_err2string
<= ldap_dn2bv(cn=Manag­er,dc=my-domain,dc=c­om)=0 Success
=> ldap_dn2bv(272)
ldap_err2string
<= ldap_dn2bv(cn=manag­er,dc=my-domain,dc=c­om)=0 Success
<<< dnPrettyNormal: <cn=Manager,dc=my-d­omain,dc=com>, <cn=manager,dc=my-d­omain,dc=com>
do_bind: version=3 dn="cn=Manager,dc=m­y-domain,dc=com" method=128
do_bind: v3 bind: "cn=Manager,dc=my-d­omain,dc=com" to "cn=Manager,dc=my-d­omain,dc=com"
send_ldap_result: conn=0 op=0 p=3
send_ldap_response:­ msgid=4 tag=97 err=0
ber_flush: 14 bytes to sd 1212
connection_get(1212­): got connid=0
connection_read(121­2): checking for input on id=0
ber_get_next
ber_get_next: tag 0x30 len 107 contents:
connection_input: conn=0 deferring operation: binding
do_search
ber_scanf fmt ({miiiib) ber:
send_ldap_result: conn=0 op=1 p=3
send_ldap_response:­ msgid=3 tag=101 err=2
ber_flush: 32 bytes to sd 1212


Thanks for help.

Michel.



This e-mail is intended only for the above addressee. It may contain privileged information.
If you are not the addressee you must not copy, distribute, disclose or use any of the information in it.
If you have received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of security reasons.
This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises.



-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


comment 1 answer | Add comment
Friday, 15 June 2007
Get VoipSWITCH+Support+­Training+All Modules In Just 1500 Usd From Solution4VOIP solution4voip 22:01:10
 Dear Friends:

Want to setup VOIP company, a business under your own brand name? We have complete solution to launche VOIP (VOice Over Internet Protocol) company. All support comes included.

Softswitch is the main element of the platform, which merges the functionality of the following VOIP architecture’s elements.

H323 switch

H323 gatekeeper

SIP Proxy

SIP registrar


Each of the described elements can operate simultaneously with the others. Moreover, the clients, regardless of the protocol, or the way they transfer connections, can connect between one another. This option allows connecting the networks, which because of the differences in implemented protocols or dialects inside the particular protocol, cannot directly transfer connection between one another. Implementing Solution4VOIP as a central traffic controller also introduces a number of additional management, supervision and network security facilitations.


The main characteristics of the softswitch include:



· Simultaneous and transparent support of SIP and H323 protocols (sip?h323 and h323?sip translator

· Possibility of implementing various types of proxy (e.g. RTP-proxy or signaling proxy), possibility of choosing proxy for each prefix defined in dialing plan.

· Advanced routing and rating system

· Full internetworking with most commercially available switches, softswitches, session border controllers and VOIP gateways.

· VOIP equipment support

· NAT support both for SIP and h323 equipment

· Calling to sip devices behind NAT (without the necessity of configuring NAT)

· Calling among users registered to softswitch, support for dynamic IP addresses

· Authentication of VOIP equipment

o by IP address

o by ANI

o by h323id

o by the pair of login/password (according to the SIP standard)

· Flexible routing

· Individual, integrated billing system

· Managing pre-paid and post-paid accounts

· Setting up users in the VSConfig program

· Managing users, blocking, setting limits

· Generating the groups of users and managing lots

· Creating and managing tariffs, the possibility of attributing a tariff to an individual user

· Data stored in the MSSQL or MySQL database

· Graphic management interface (presentation of the statistical data, billing information, managing clients’ accounts, generating PIN, managing the tariffs, dialing plan and others)

· Graphic interface presenting the current traffic in the real time, number of the logged in clients, with the division into different types of services, presentation of logs and others

· Web interface for clients – presentation of the connections history, possibility of exporting to the file, presentation of the current account status, possibility of making payments online and others

· Easy to set up architecture

· Automatic software re-start facilities in case of system failure

· Scalability for new telecommunication services by enabling additional modules



Advantages of managing the system:


· Simplify the management processes and network configuration changes of VoIP equipment

· Unify equipment supporting different protocols (or dialects of one protocol)

· Manage concentration and routing processes of VoIP traffic

· Centralize authorization and billing tasks of VoIP calls in one point

· Hide the network structure from third parties, if necessary

· Utilize possibility of implementing value-added services such as: calling card and DID calling card system, IPPBX, SMS/ANI/PIN/DID callback system.



STANDARD APPLICATIONS


Central point of your VOIP network



Main benefits:


Management of authorization rules of VoIP-gateways

Setting up call routing rules

Provisioning of compatibility for H323 and SIP- equipment of various vendors

Security and load planning of VoIP-traffic by using optional RTP-proxying

Access to the statistical data (ASR, PDD and others)

Transparent interface of the billing system



Network security



When using RTP-proxying SoftSwitch provides a single entry point for VoIP traffic.Both for clients and carriers there is only one IP address available.

Integration of equipment with support of different protocols

One of the most important features of RSF1000 is its ability to support widely accepted signaling IP-protocols - SIP and H323. The system provides transparent converging of one protocol into another, thus allowing performing calls from one type of equipment to another.



SCALABILITY


Through launching subsequent modules, it is very convenient for a provider to extend the range of services offered. Available modules:

IVR for calling cards

Web/SMS/ANI callback (with IVR)

Reseller’s module

Online shop

CallShop



SPECIFICATIONS


Supported protocols


1 H.323 v.2 (H.245 v7, H225 v4) with/without FAST START

2 SIP (RFC 3261)

3 proxying of RTP/RTCP streams

4 Signalling proxy

5 Support of T38 (SIP, H323)

6 Transparent conversion of SIP to H323 and vice versa



Support of the Devices Behind the NAT


1 SIP-devices

2 H323-devices



Authentication


1 by IP address – SIP and H323

2 by H323ID – h323 terminals/gateways

3 by ANI (calling party number) – SIP and H323

4 by login and password- SIP equipment

5 by login and password – HearLink pc to phone/web to phone dialer (included in the package)

6 gatekeeper registration based on aliases



Intelligent routing


1 based on prefixes (the possibility of defining prefixes differentiating individual users)

2 based on accessibility of the VOIP gateway

3 based on priorities when choosing a gateway

4 depending on available voice codecs

5 depending on prefixes specified in the tariff of an individual client


Phone Numbers Translation


1 Deletion of the set number of digits from the called party number

2 Addition of the set number of digits to the called party number

3 Deletion of the set number of digits from the caller number

4 Addition of the set number of digits to the caller number

5 Virtual prefixes (for differentiation of the dialing plans)



Information for the Billing System


1 Real-time, built in billing system

2 Storage in SQL database (MSSQL or MYSQL)

3 pre-paid and post-paid accounts

4 Payments history

5 CDR – examining the logs of the calls carried out from the VSCConfig level, possibility of filtering data according to the set parameters, possibility of exporting data to the file (html, excel, txt, or csv type), presenting the CDR on the WWW pages available for clients



System Management and Control Features


1 Graphic User Interface for managing the overall functionality of the system

2 Visual presentation of current connections along with the information on their status

3 The number of statistical data presenting the information on the traffic intensity with its various parameters e.g. ASR, PDD. Possibility of limiting the number of data presented by using available filters e.g. only incoming traffic from the particular client, traffic directed to the particular gateway, or prefix etc.

4 Visual presentation of logged in clients and their current status, with the division into types of services e.g. gatekeeper users, SIP users, pc2phone, callback.



Operating Systems

1 Windows 2000, 2003, XP


-------------------­--------------------­--------------------­- -----

Contact us if you are interested.


Thank you,
Solution4voip.com
VOIP Solution Provider
Solution for Voice Over Internet Protocol (VOIP)

Email: salesATsolution4voi­pDOTcom
MSN: SalesATsolution4voi­pDOTcom, SupportATsolution4v­oipDOTcom
Phone: +1 888 8679193
Add comment
Saturday, 2 June 2007
Permissions Webmaster 12:13:33
 I have a server that will not let the user change permissions when he tries says that he is not an apache user any ideas on what is causing this or how to fix it?
comment 88 answers | Add comment
Friday, 1 June 2007
Session Cache is not configured Ray Hillman 17:06:01
 Hi,

I've just installed a test Apache 2.0.39 with mod_ssl enabled.
Apache is starting, but I'm getting the following
message in the access_log file when I restart:

[Tue Jun 25 13:18:15 2002] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Tue Jun 25 13:18:18 2002] [notice] Apache/2.0.39 (Unix) mod_ssl/2.0.39
OpenSSL/0.9.7-dev configured -- resuming normal operations

I've generated a private test certificate and pointed
SSLCertificateFile at it. SSLSessionCache is the default
(dbm:/logs/ssl_scac­he).

Have I missed something? How do I configure
the Session Cache?

Thanks

Ray

--
RFC-822 : R.K.Hillman@bton.ac­.uk
X.400 : S=hillman; G=ray; O=bton; PRMD=uk.ac; ADMD= ; C=GB
Tel : +44 1273 600900 Ext. 2644 or +44 1273 642644 (direct)
Fax : +44 1273 642666
Http : http://www.bton.ac.­uk/
http://sirius.admin­.bton.ac.uk/backhand­er/
Systems Manager, University of Brighton Information Services,
Watts Building, Moulsecoomb, Brighton, East Sussex, UK, BN2 4GJ
comment 2 answer | Add comment
Tuesday, 22 May 2007
[error] (9)Bad file descriptor: apr_socket_accept: (client socket) Guest 22:38:08
 I've spent hours googling and asked about this error message on a PHP list and was directed here.

Every time I gracefully restart Apache 2.2.2, the error log reports:

[Thu May 18 19:59:29 2006] [notice] Graceful restart requested, doing restart
[Thu May 18 19:59:29 2006] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Thu May 18 19:59:30 2006] [notice] Apache configured -- resuming normal operations
[Thu May 18 19:59:30 2006] [warn] long lost child came home! (pid 2881)

On rare occasion, Apache 2.2.2 is crashing with:
[Fri May 19 17:29:05 2006] [notice] child pid 11243 exit signal Segmentation fault (11)
(Long list, all the child pids different of course.)

I've searched the bug list and found nothing for apr_socket_accept. From googling, I've found messages about errors with apr_socket_accept in very old versions of Apache, but none seemed helpful.

Since I see "client socket", it certainly sounds like it's an interaction with something else that's causing the problem, but I don't know how to determine what that something else is. I could include my strace, but it's long and I'm not a progammer so I can't really get anywhere with it.

I get the same error even if I take out the only external module I use (PHP5.1.4). I've tried using a totally stripped-down version of httpd.conf as well, with the same results. I've tried building Apache without some of the standard modules, with the same results. (The list of modules is below.)

It seems possibly related to my operating/build environment:
gcc version 3.3.5 (Debian 1:3.3.5-13)
ReiserFS on (software) RAID-1
Linux version 2.6.8-11-amd64-gene­ric
Debian Stable

dmesg reports no file system errors. I did reboot the system once, and ReiserFS reported no problems. The only thing left that I can think of is to bring down the server and run reiserfsck. It's a production server, so I very much dislike doing it unless someone believes that this error points towards the file system.

Any suggestions appreciated.

Thank you,

Jeff Hill


# apachectl -l
core.c
mod_authn_file.c
mod_authn_default.c­
mod_authz_host.c
mod_authz_groupfile­.c
mod_authz_user.c
mod_authz_default.c­
mod_auth_basic.c
mod_cache.c
mod_mem_cache.c
mod_include.c
mod_filter.c
mod_deflate.c
mod_log_config.c
mod_env.c
mod_usertrack.c
mod_setenvif.c
mod_ssl.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_asis.c
mod_info.c
mod_cgi.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_speling.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_so.c



-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


comment 4 answer | Add comment
Wednesday, 16 May 2007
Apache::Reload [ was Re: [Fwd: foundation: r10592 - in /foundation/officer­s: cclas.txt grants.txt]] Fred Moyer 13:29:59
 Philip M. Gollucci wrote:
[dropped all but dev@]
Fred Moyer wrote:
Also, there are a couple patches sent to -user or -dev in 2006 worth
investigating incorporating.

I applied that patch a few days ago. Philip I've stolen your
Makefile.PL from Apache::SizeLimit and hacked it to fit Apache::Reload.

I still need to write some tests for this (none existing), eta on the
release right now is 'a few weeks'. Sorry I haven't been able to move
faster on this, have been involved in a big push at the day job. I'll
post my tests to the list for review before I commit, thanks for your
patience on this.
Add comment
Tuesday, 15 May 2007
is APR intended to work with threads? Torsten Foertsch 14:01:56
 $ perl -MAPR::Pool -Mthreads -e '
APR::Pool->new;
$_->join for (map {threads->create(su­b{})} 1,2);print "DONE\n"'
DONE

but

$ perl -MAPR::Pool -Mthreads -e '
my $p=APR::Pool->new;
$_->join for (map {threads->create(su­b{})} 1,2); print "DONE\n"'
DONE
*** glibc detected *** perl: double free or corruption (!prev): 0x0820e670 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7e4c6e1]
/lib/libc.so.6(cfre­e+0x89)[0xb7e4dd79]
/opt/apache22-worke­r/lib/libapr-1.so.0(­apr_allocator_destro­y+0x44)[0xb7b87b59]
/opt/apache22-worke­r/lib/libapr-1.so.0(­apr_pool_destroy+0x1­17)[0xb7b88647]
/opt/apache22-worke­r/lib/libapr-1.so.0(­apr_pool_terminate+0­x46)[0xb7b8820e]
/opt/apache22-worke­r/lib/libapr-1.so.0(­apr_terminate+0x30)[0xb7b897e6]
/opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/APR.so(XS_­APR_END+0x59)[0xb7fb5d39]
perl(Perl_pp_enters­ub+0x3c3)[0x80caef3]
perl[0x8062f7d]
perl(Perl_call_sv+0­x6d4)[0x8067434]
perl(Perl_call_list­+0x27f)[0x806790f]
perl(perl_destruct+­0x12e1)[0x8069961]
perl(main+0xc6)[0x80601b6]
/lib/libc.so.6(__li­bc_start_main+0xdc)[0xb7dfdf9c]
perl[0x8060061]
======= Memory map: ========
08048000-08160000 r-xp 00000000 03:05 129870 /usr/bin/perl
08160000-08165000 rw-p 00117000 03:05 129870 /usr/bin/perl
08165000-082fb000 rw-p 08165000 00:00 0 [heap]
b6800000-b6821000 rw-p b6800000 00:00 0
b6821000-b6900000 ---p b6821000 00:00 0
b6952000-b6953000 ---p b6952000 00:00 0
b6953000-b7153000 rw-p b6953000 00:00 0
b7174000-b7175000 ---p b7174000 00:00 0
b7175000-b7975000 rw-p b7175000 00:00 0
b7996000-b79a7000 r-xp 00000000 03:05 32517 /lib/libz.so.1.2.3
b79a7000-b79a9000 rw-p 00010000 03:05 32517 /lib/libz.so.1.2.3
b79a9000-b7ac4000 r-xp 00000000 03:05 260697 /usr/lib/libcrypto.­so.0.9.8
b7ac4000-b7aca000 r--p 0011b000 03:05 260697 /usr/lib/libcrypto.­so.0.9.8
b7aca000-b7ad9000 rw-p 00121000 03:05 260697 /usr/lib/libcrypto.­so.0.9.8
b7ad9000-b7adc000 rw-p b7ad9000 00:00 0
b7adc000-b7b15000 r-xp 00000000 03:05 260698 /usr/lib/libssl.so0.9.8
b7b15000-b7b19000 rw-p 00039000 03:05 260698 /usr/lib/libssl.so0.9.8
b7b19000-b7b2f000 r-xp 00000000 03:05 259608 /usr/lib/libsasl2.s­o.2.0.22
b7b2f000-b7b31000 rw-p 00015000 03:05 259608 /usr/lib/libsasl2.s­o.2.0.22
b7b31000-b7b40000 r-xp 00000000 03:05 32488 /lib/libresolv-2.5.­so
b7b40000-b7b42000 rw-p 0000e000 03:05 32488 /lib/libresolv-2.5.­so
b7b42000-b7b44000 rw-p b7b42000 00:00 0
b7b4f000-b7b59000 r-xp 00000000 03:05 32504 /lib/libgcc_s.so.1
b7b59000-b7b5b000 rw-p 00009000 03:05 32504 /lib/libgcc_s.so.1
b7b5b000-b7b61000 r-xp 00000000 03:05 681480 /usr/lib/perl5/5.8.­8/i586-linux-thread-­multi/auto/threads/hreads.so
b7b61000-b7b63000 rw-p 00005000 03:05 681480 /usr/lib/perl5/5.8.­8/i586-linux-thread-­multi/auto/threads/hreads.so
b7b63000-b7b67000 r-xp 00000000 03:05 1395452 /opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/Pool/Pool.­so
b7b67000-b7b68000 r--p 00003000 03:05 1395452 /opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/Pool/Pool.­so
b7b68000-b7b69000 rw-p 00004000 03:05 1395452 /opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/Pool/Pool.­so
b7b69000-b7b70000 r-xp 00000000 03:05 32490 /lib/librt-2.5.so
b7b70000-b7b72000 rw-p 00006000 03:05 32490 /lib/librt-2.5.so
b7b72000-b7b99000 r-xp 00000000 03:05 1266919 /opt/apache22-worke­r/lib/libapr-1.so.0.­2.7
b7b99000-b7b9a000 r--p 00026000 03:05 1266919 /opt/apache22-worke­r/lib/libapr-1.so.0.­2.7
b7b9a000-b7b9b000 rw-p 00027000 03:05 1266919 /opt/apache22-worke­r/lib/libapr-1.so.0.­2.7
b7b9b000-b7bb9000 r-xp 00000000 03:05 571254 /usr/lib/libexpat.s­o.1.5.0
b7bb9000-b7bba000 r--p 0001d000 03:05 571254 /usr/lib/libexpat.s­o.1.5.0
b7bba000-b7bbc000 rw-p 0001e000 03:05 571254 /usr/lib/libexpat.s­o.1.5.0
b7bbc000-b7c00000 r-xp 00000000 03:05 571803 /usr/lib/libsqlite.­so.0.8.6
b7c00000-b7c03000 rw-p 00043000 03:05 571803 /usr/lib/libsqlite.­so.0.8.6
b7c03000-b7c5c000 r-xp 00000000 03:05 571799 /usr/lib/libsqlite3­.so.0.8.6
b7c5c000-b7c5e000 rw-p 00059000 03:05 571799 /usr/lib/libsqlite3­.so.0.8.6
b7c5e000-b7c94000 r-xp 00000000 03:05 259925 /usr/lib/libldap-2.­3.so.0.2.15
b7c94000-b7c96000 rw-p 00035000 03:05 259925 /usr/lib/libldap-2.­3.so.0.2.15
b7c96000-b7cb2000 r-xp 00000000 03:05 1266952 /opt/apache22-worke­r/lib/libaprutil-1.s­o.0.2.7
b7cb2000-b7cb3000 r--p 0001b000 03:05 1266952 /opt/apache22-worke­r/lib/libaprutil-1.s­o.0.2.7
b7cb3000-b7cb4000 rw-p 0001c000 03:05 1266952 /opt/apache22-worke­r/lib/libaprutil-1.s­o.0.2.7
b7cb4000-b7cd5000 rw-p b7cb4000 00:00 0
b7cd5000-b7d10000 r--p 00000000 03:05 617761 /usr/lib/locale/en_­US.utf8/LC_CTYPE
b7d10000-b7de7000 r--p 00000000 03:05 617762 /usr/lib/locale/en_­US.utf8/LC_COLLATE
b7de7000-b7de8000 rw-p b7de7000 00:00 0
b7de8000-b7f10000 r-xp 00000000 03:05 32460 /lib/libc-2.5.so
b7f10000-b7f11000 r--p 00128000 03:05 32460 /lib/libc-2.5.so
b7f11000-b7f13000 rw-p 00129000 03:05 32460 /lib/libc-2.5.so
b7f13000-b7f16000 rw-p b7f13000 00:00 0
b7f16000-b7f2a000 r-xp 00000000 03:05 32486 /lib/libpthread-2.5­.so
b7f2a000-b7f2c000 rw-p 00013000 03:05 32486 /lib/libpthread-2.5­.so
b7f2c000-b7f2e000 rw-p b7f2c000 00:00 0
b7f2e000-b7f30000 r-xp 00000000 03:05 32494 /lib/libutil-2.5.so­
b7f30000-b7f32000 rw-p 00001000 03:05 32494 /lib/libutil-2.5.so­
b7f32000-b7f33000 rw-p b7f32000 00:00 0
b7f33000-b7f3c000 r-xp 00000000 03:05 32464 /lib/libcrypt-2.5.s­o
b7f3c000-b7f3f000 rw-p 00008000 03:05 32464 /lib/libcrypt-2.5.s­o
b7f3f000-b7f66000 rw-p b7f3f000 00:00 0
b7f66000-b7f8a000 r-xp 00000000 03:05 32468 /lib/libm-2.5.so
b7f8a000-b7f8c000 rw-p 00023000 03:05 32468 /lib/libm-2.5.so
b7f8c000-b7f8e000 r-xp 00000000 03:05 32466 /lib/libdl-2.5.so
b7f8e000-b7f90000 rw-p 00001000 03:05 32466 /lib/libdl-2.5.so
b7f90000-b7fa2000 r-xp 00000000 03:05 32471 /lib/libnsl-2.5.so
b7fa2000-b7fa4000 rw-p 00011000 03:05 32471 /lib/libnsl-2.5.so
b7fa4000-b7fa6000 rw-p b7fa4000 00:00 0
b7fa6000-b7fb2000 r-xp 00000000 03:05 259923 /usr/lib/liblber-2.­3.so.0.2.15
b7fb2000-b7fb4000 rw-p 0000b000 03:05 259923 /usr/lib/liblber-2.­3.so.0.2.15
b7fb4000-b7fb8000 r-xp 00000000 03:05 1395418 /opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/APR.so
b7fb8000-b7fb9000 r--p 00003000 03:05 1395418 /opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/APR.so
b7fb9000-b7fba000 rw-p 00004000 03:05 1395418 /opt/apache22-worke­r/mod_perl/5.8.8/i58­6-linux-thread-multi­/auto/APR/APR.so
b7fba000-b7fbb000 r--p 00000000 03:05 617743 /usr/lib/locale/en_­US.utf8/LC_NUMERIC
b7fbb000-b7fbc000 r--p 00000000 03:05 601630 /usr/lib/locale/en_­US.utf8/LC_TIME
b7fbc000-b7fbd000 r--p 00000000 03:05 601629 /usr/lib/locale/en_­US.utf8/LC_MONETARY
b7fbd000-b7fbe000 r--p 00000000 03:05 617736 /usr/lib/locale/en_­US.utf8/LC_MESSAGES/­SYS_LC_MESSAGES
b7fbe000-b7fbf000 r--p 00000000 03:05 617668 /usr/lib/locale/en_­US.utf8/LC_PAPER
b7fbf000-b7fc0000 r--p 00000000 03:05 617691 /usr/lib/locale/en_­US.utf8/LC_NAME
b7fc0000-b7fc1000 r--p 00000000 03:05 601626 /usr/lib/locale/en_­US.utf8/LC_ADDRESS
b7fc1000-b7fc2000 r--p 00000000 03:05 617653 /usr/lib/locale/en_­US.utf8/LC_TELEPHONE­
b7fc2000-b7fc3000 r--p 00000000 03:05 617654 /usr/lib/locale/en_­US.utf8/LC_MEASUREME­NT
b7fc3000-b7fca000 r--s 00000000 03:05 600904 /usr/lib/gconv/gcon­v-modules.cache
b7fca000-b7fcb000 r--p 00000000 03:05 601627 /usr/lib/locale/en_­US.utf8/LC_IDENTIFIC­ATION
b7fcb000-b7fcc000 rw-p b7fcb000 00:00 0
b7fcc000-b7fcd000 r-xp b7fcc000 00:00 0 [vdso]
b7fcd000-b7fe8000 r-xp 00000000 03:05 32453 /lib/ld-2.5.so
b7fe8000-b7fea000 rw-p 0001a000 03:05 32453 /lib/ld-2.5.so
bfeae000-bfec4000 rw-p bfeae000 00:00 0 [stack]
Aborted


At least 2 threads need to be created. It crashes also if $p in undefined
between thread creation and joining but it does not if it is undefined before
thread creation.

Perl: 5.8.8
mod_perl: trunk
httpd: 2.2.3

Torsten
Add comment
Sunday, 13 May 2007
RewriteRule: Parenthesis not capturing Garth Winter Webb 13:26:42
 Hello, I'm trying to use the RewriteRule directive to rewrite a simple
request. I've added these lines to a VirtualHost section of an apache
running on 'my.host' listening on port 80:

RewriteEngine on

RewriteLog "/tmp/rewrite.log"
RewriteLogLevel 9
RewriteRule ^/(.+) http://my.host:8600­/somepath/$1 [P]

When I make a request like this:

http://my.host/foo

I see these 5 lines in my rewrite log:


192.168.1.124 - - [16/Feb/2003:12:14:09 -0800]
[my.host/sid#80d18a4][rid#80e0794/initial] (2) init rewrite engine with
requested uri /foo
192.168.1.124 - - [16/Feb/2003:12:14:09 -0800]
[my.host/sid#80d18a4][rid#80e0794/initial] (3) applying pattern '^/(.*)'
to uri '/foo'
192.168.1.124 - - [16/Feb/2003:12:14:09 -0800]
[my.host/sid#80d18a4][rid#80e0794/initial] (2) rewrite /foo ->
http://my.host:8600­/somepath/
192.168.1.124 - - [16/Feb/2003:12:14:09 -0800]
[my.host/sid#80d18a4][rid#80e0794/initial] (2) forcing proxy-throughput
with http://my.host:8600­/somepath/
192.168.1.124 - - [16/Feb/2003:12:14:09 -0800]
[my.host/sid#80d18a4][rid#80e0794/initial] (1) go-ahead with proxy
request proxy:http://my.hos­t:8600/somepath/ [OK]


For some reason the parenthesis are not capturing and $1 contains an
empty string. The parenthesis HAD to match because otherwise the rule
("A '/' followed by at least one character") would have failed and I
would not have gotten these log messages. What am I missing here?

Thanks,

--
Garth Winter Webb <garth@perijove.com­>

-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


comment 2 answer | Add comment
Friday, 11 May 2007
RFC: Devel::Profiler::Pl­ugins::Template Geoffrey Young 18:13:37
 hi all :)­

I spent some time this week adding hooks for template toolkit into
Devel::Profiler. you can find the code here

http://www.modperlc­ookbook.org/~geoff/m­odules/experimental/­Devel-Profiler-Plugi­ns-Template-0.01.tar­.gz

I'm not entirely convinced of the namespace, which is why it's not on
CPAN yet. but I'd appreciate it if folks could give it a whirl when
they have the chance.

--Geoff

from the docs:

use Devel::Profiler::Pl­ugins::Template; # enable TT hooks
use Devel::Profiler; # required

...

much hackery is involved, so it's not guaranteed
to work on all platforms, versions of perl, or versions of TT.
but if it does work, your C<dprofpp> results will look like this

%Time ExclSec CumulS #Calls sec/call Csec/c Name
3.20 0.048 0.048 1794 0.0000 0.0000 Encode::_utf8_on
1.27 0.019 0.028 2 0.0095 0.0140 TT::PROCESS::get_st­andard_nav
0.00 0.000 0.000 2 0.0000 0.0000
TT::INCLUDE::layout­_2fframe_2fhead_2ett­

which corresponds to something like

[% BLOCK get_standard_nav %]
...
[% END %]

[% PROCESS get_standard_nav %]
[% INCLUDE layout/frame/head.t­t %]

note that the TT results are right alongside of your normal perl calls,
which I find very convenient.

...

oh, and this probably won't work so well unless you have the current
Devel::Profiler code from svn:

http://sourceforge.­net/projects/devel-p­rofiler/

but it might.
Add comment
Thursday, 10 May 2007
Mod_proxy _balancer and weblogic 8.1 Arun Kumar 06:10:57
 Hi all,

We plan to use mod_proxy_balancer in our environment...our backend server is weblogic 8.1 sp2.

we currently using apache 2.2 and weblogic..... weblogic 8.1 is not having plugin for apache 2.2 therefore we plan to go for mod_proxy

Please let me session stickiness will work in mod_proxy_balancer and weblogic.

Regards,
Arun


-------------------­--------------
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
comment 1 answer | Add comment
Wednesday, 9 May 2007
explaining the dcfg bug (was: What can I do ...) Torsten Foertsch 14:30:52
 Hi Fred,

On Wednesday 09 May 2007 10:42, Fred Moyer wrote:
I have been following this somewhat, but not grokking all of it.
Can you write a test that shows the change and its effect?
I was poking around that area of the code for the stacked handlers bug
so I understand some of it but a test would be really be helpful here.

Well, I have thought of that myself but I was not able to produce a simple
test case. It is simple to get the memory corrupted (just call
$r->push_handlers twice for the same phase) but it's hard to predict when the
segfault will occur since it depends completely on your memory mgmt
implementation.

But I can explain the bug more thoroughly.

modperl_handler_loo­kup_handlers is declared this way:

MpAV **modperl_handler_l­ookup_handlers(modpe­rl_config_dir_t *dcfg,
modperl_config_srv_­t *scfg,
modperl_config_req_­t *rcfg,
apr_pool_t *p,
int type, int idx,
modperl_handler_act­ion_e action,
const char **desc)

It is called at startup to configure handlers in server/per_dir config and at
request time to configure handlers in request config.

At startup when there is no request it is called with rcfg==0. p is in this
case a longer living pool.

At request time it is passed rcfg!=0 and the request pool in p.

The function initializes avp=0 and ravp=0.

Then it says

avp = &dcfg->handlers_per­_dir[idx];
if (rcfg) {
ravp = &rcfg->handlers_per­_dir[idx];
}

(The scfg->handlers_per_­srv case is similar)

So, avp now points to an array element inside dcfg while ravp at request time
points to an array element inside rcfg. At startup it remains 0.

Later the function ensures that avp!=0 and then does this

if (ravp && !*ravp) {
if (*avp) {
/* merge with existing configured handlers */
*ravp = apr_array_copy(p, *avp);
}
else {
/* no request handlers have been previously pushed or set */
*ravp = modperl_handler_arr­ay_new(p);
}
}
else if (!*avp) {
/* directly modify the configuration at startup time */
*avp = modperl_handler_arr­ay_new(p);
}

The arrays dcfg->handlers_per_­dir and rcfg->handlers_per_­dir are initially set
to all NULL pointers. If an element is 0 it means there is no handler set for
this phase. Otherwise it points to an apr_array.

So, at startup time we have to make sure that *avp points to an apr_array and
return that while at request time *ravp should point to an apr_array and that
should be returned.

Let's first look what happens at startup. rcfg==NULL and hence ravp==NULL.
The "else if" checks whether the appropriate element of dcfg is already
initialized. If not it is assigned an empty apr_array. Here the program works
correct.

Now at request time. rcfg!=NULL and hence ravp!=NULL. *ravp may be NULL if
there is no handler set yet.

The "if (ravp && !*ravp)" works correct if *ravp is NULL. In this case (the
first time $r->push_handlers is called) *ravp gets initialized.

But if the code is run a second time the if condition is false because *ravp
is already set. In this case we must do nothing but simply return ravp.

So we hit the else if branch. If now *avp is NULL we initialize it. And this
is wrong. To cite from Nick Kew book:

When processing a request, use the fields of the request_rec - in
particular, the request pool and the request configuration vector.
Treat everything else as read-only.

In our case we modify a structure which is valid until server shutdown and
write there a pointer that is allocated from the request pool since p in

*avp = modperl_handler_arr­ay_new(p);

is the request pool.

So how can it be that *avp is NULL at request time? That simply means there
has been no handler configured at startup time.

What possible solutions are there? Let's have a look at the code for the other

case MP_HANDLER_ACTION_S­ET:

Here it says

if (ravp) {
}
else if (*avp) {
}
else {
}

This is correct because no else branch is entered if ravp!=NULL.

For the ACTION_PUSH case we can do it the same way:

if (ravp) {
if( !*ravp ) {
if (*avp) {
/* merge with existing configured handlers */
*ravp = apr_array_copy(p, *avp);
}
else {
/* no request handlers have been previously pushed or set
*/
*ravp = modperl_handler_arr­ay_new(p);
}
}
}
else if (!*avp) {
/* directly modify the configuration at startup time */
*avp = modperl_handler_arr­ay_new(p);
}

or the way the original patch did:

if (ravp && !*ravp) {
}
else if (ravp) {
/* ravp is already initialized: do nothing */
}
else if (!*avp) {
}

So the bug reduces to

if (a) {
if (b) {
}
} else if (c) {
}

not being the same as

if (a && b) {
} else if (c) {
}

Hope that helps,
Torsten
Add comment
Saturday, 5 May 2007
Can apache 2.0.52 impact a Subversion lock-file command? Ted Trahan 23:50:36
 I am using Subversion and accessing it through Apache (http protocol).
Both Subversion and Apache are running
on a Red Hat Enterprise Linux server. TortoiseSVN is the Subversion
client running on Windows XP.

We have the following revisions:
RHEL 4WS
Httpd 2.0.52
Subversion 1.3.2
TortoiseSVN 1.3.5

Problem: I am able to read and write to the project in the repository.
However, executing a file-lock command returns
"Error: Lock request failed: 405 Method Not Allowed (http://mydomain)".­

My understanding is that failure to lock a file archived in a source
code control repository such as
Subversion is not the same as the LockFile apache maintains as specified
in the LockFile directive.
Therefore I don't believe this is related to Apache's ability to access
its own LockFile.

The permissions on the server's /home/svn/<repos>/l­ocks directory are
the same as other repository
directories (conf/, hooks/, etc) which work, so I wouldn't expect this
to be a permissions problem.

In a search of the web and list archives, I find two reasons why the
lock command might not work:
-the feature is not supported by the version of apache
-the feature was not available prior to Subversion 1.2.1

I have a more recent version of Subversion, so I don't believe that to
be a cause of the problem.
Also, I find little in the Apache FAQ regarding file locking in general,
let alone file lock problems since this apache release.

I get the same error using both TSVN and (as a sanity check) svn.exe.
So I don't think it's a configuration problem
specific to the TortoiseSVN client.

Any ideas where else I might look? Any ideas on whether Apache really
has an impact on Subversion's file-lock
command?

I appreciate any help you can give me.

Thanks,
Ted


-------------------­--------------------­--------------------­----------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.a­pache.org/userslist.­html> for more info.
To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org
" from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg
For additional commands, e-mail: users-help@httpd.ap­ache.org


Add comment
Thursday, 3 May 2007
threaded server + scope=handler: modperl_response_ha­ndler vs. modperl_response_ha­ndler_cgi Torsten Foertsch 15:32:45
 Hi,

in case of a threaded server modperl_response_ha­ndler runs this code:

#ifdef USE_ITHREADS
interp = modperl_interp_sele­ct(r, r->connection, r->server);
aTHX = interp->perl;
#endif

while modperl_response_ha­ndler_cgi runs this:

#ifdef USE_ITHREADS
interp = modperl_interp_sele­ct(r, r->connection, r->server);
aTHX = interp->perl;
if (MpInterpPUTBACK(in­terp)) {
rcfg->interp = interp;
}
#endif

then both call via modperl_response_ha­ndler_run and modperl_callback_pe­r_dir
modperl_callback_ru­n_handlers which does then:

#ifdef USE_ITHREADS
if (r && !c && modperl_interp_scop­e_connection(scfg)) {
c = r->connection;
}
if (r || c) {
interp = modperl_interp_sele­ct(r, c, s);
aTHX = interp->perl;
}
else {
/* Child{Init,Exit}, OpenLogs */
aTHX = scfg->mip->parent->­perl;
PERL_SET_CONTEXT(aT­HX);
}
#endif

This means in both cases modperl_interp_sele­ct is called twice but for the
perl-script case rcfg->interp = interp is set.

modperl_interp_sele­ct first looks if rcfg->interp is set and returns it. Only
if it's not it looks at other places for an interpreter.

This means a perl-script handler needs 1 interpreter to handle the response
phase while a modperl handler needs 2.

I noticed that with "PerlTrace i". I had installed handlers for Trans,
MapToStorage, Fixup and Response. 2 interpreters were configured.

With a modperl handler I got this:

After Fixup:
modperl_tipool_putb­ack_base: all items idle:
interp_pool_dump: listp==0x9467668, interp==0x8277740, requests=3
interp_pool_dump: listp==0xb78f2a0, interp==0xa3385a0, requests=0

"requests=3" means modperl_interp_sele­ct was run 3 times, once for Trans, once
for MapToStorage and once for Fixup.

After Response:
modperl_tipool_putb­ack_base: all items idle:
interp_pool_dump: listp==0x9467668, interp==0x8277740, requests=4
interp_pool_dump: listp==0xb78f2a0, interp==0xa3385a0, requests=1

Now it shows requests=4 for the first interpreter but requests=1 for the 2nd.
I would have expected requests=4 and requests=0.

After scrutinizing the code I tried a perl-script handler and got this output.

After Fixup:
modperl_tipool_putb­ack_base: all items idle:
interp_pool_dump: listp==0xc1235e8, interp==0x87ef068, requests=3
interp_pool_dump: listp==0xa5315e8, interp==0xc7ee558, requests=0

After Response:
modperl_tipool_putb­ack_base: all items idle:
interp_pool_dump: listp==0xc1235e8, interp==0x87ef068, requests=4
interp_pool_dump: listp==0xa5315e8, interp==0xc7ee558, requests=0

This is what I'd have expected.

Torsten
comment 1 answer | Add comment
Wednesday, 2 May 2007
PerlCleanupHandler semantic? Torsten Foertsch 16:47:56
 Hi,

what should the exact semantic of a PerlCleanupHandler be when
PerlInterpScope==ha­ndler?

I am not asking what it is but what it should be.

A PerlCleanupHandler can be installed in httpd.conf or via $r->add_config or
by $r->{push|set}_hand­lers.

a) all cleanup handlers are called when the request is over. In this case I
think the interpreter should stick to the request just like with
scope==request.

b) cleanups are called when the interpreter is released. With scope==handler
this means cleanups are run just after the first phase that needs an
interpreter. Now one can argue that only the cleanups installed by
{push|set}_handlers­ in the same phase are to be called when the interpreter is
destroyed but handlers installed via httpd.conf or add_config are to be
called when the request is over. Variations on this theme are possible.

Torsten
comment 1 answer | Add comment
Tuesday, 1 May 2007
Interpreter scope Torsten Foertsch 21:16:36
 Hi,

the default interpreter scope is request. That means a certain interpreter is
locked during the whole request cycle. I use modperl mostly in the
pre-response phases plus sometimes as an output filter. But I use pnotes to
pass data between the phases. If I understand it correctly this forbids a
handler interpreter scope. Now I'd like to release the interpreter in most
cases just before the response phase. So it can be reused by another request
while the current request sends its data over a possibly slow network.

Is that reasonable?

Is there something like $r->release_interp_­after_this_phase()?

If not what is the right place to start looking/patching? And what pitfalls
are there to watch out?

Torsten
comment 3 answer | Add comment
Re: threaded server + scope=handler + PerlCleanupHandler:­ another similar bug Torsten Foertsch 14:24:10
 On Monday 30 April 2007 22:22, Philippe M. Chiasson wrote:
And that doesn't seem logical at all. In all cases, since the initial int=
erpreter
is tied up in modperl_response_ha­ndler() a new one shouldn't be needed to=
dispatch
that handler part.

I have found similar bug. Try

$r->push_handlers(P­erlCleanupHandler=>'­some_named_function'­)

from a TranslationHandler or so.

modperl_interp_unse­lect calls modperl_config_requ­est_cleanup -->
modperl_config_requ­est_cleanup --> modperl_callback_pe­r_dir -->
modperl_callback_ru­n_handlers --> modperl_interp_sele­ct.

modperl_interp_sele­ct then selects another interpreter to do the cleanup.

Then at the end of modperl_callback_ru­n_handlers modperl_interp_unse­lect is
called for the interpreter that did the cleanup. Now the story repeats eating
up all interpreters.

When push_handlers is called from a mod_perl response handler the same
behavior is seen due to the previous bug, the missing rcfg->interp.

However with a perl-script handler something changes. Now the right interp is
found in rcfg->interp. But nevertheless it recurses because
modperl_callback_ru­n_handlers calls modperl_interp_unse­lect while
modperl_callback_ru­n_handlers was actually called from
modperl_interp_unse­lect. In the end I got a segfault.

So, I think either modperl_interp_unse­lect or modperl_config_requ­est_cleanup
needs a flag that says "do not recurse". Maybe interp->flags is a good place
for a flag that says "in unselect" or so.

Or maybe a cleaner way is to use interp->refcnt. Simply increment it each time
modperl_interp_sele­ct returns it. For what I can see refcnt isn't used at all
by now. Yes, on a second thought that is what I'd prefer.

Thoughts?

Torsten
Add comment
Friday, 27 April 2007
Re: Logging With Mod Perl 2.0 Torsten Foertsch 13:00:01
 On Thursday 26 April 2007 21:10, Tyler Bird wrote:
But I was wondering isn't there anything I can do to mod_perl that will
allow a plain warn to send it to my virtualhosts log and not my servers
log.
without using the $r->warn() syntax

The problem is you need a $r object for that. In MP1 there was a global one.
In MP2 there is not.

Your problem can possibly be solved by using PerlOptions +GlobalRequest plus
modifying the warn function by either setting $SIG{__WARN__} or
*CORE::GLOBAL::warn­=sub{...}

*CORE::GLOBAL::warn­=sub {
(Apache2::RequestUt­il->request || Apache2::ServerUtil­->server)->warn(@_);­
}

Torsten
Add comment
Thursday, 26 April 2007
Re: MP 2.0.3 & Apache 2.2.3 -> auth tests fail Geoffrey Young 22:23:43
 
Back to 2.2.4 - MP2.0.3 worked with one alteration. It seems that > ap_get_server_versi­on is not only depreciated, but also changed > functionality. That is... one test fails because it calls > get_server_version,­ expects "Apache 2.2.4 (Unix)" but gets "Apache > 2.2.4".

ugh. I guess we haven't been paying attention. the relevant changes
are these:

Changes with Apache 2.2.4

*) The full server version information is now included in the error log at
startup as well as server status reports, irrespective of the setting
of the ServerTokens directive. ap_get_server_versi­on() is now
deprecated, and is replaced by ap_get_server_banne­r() and
ap_get_server_descr­iption(). [Jeff Trawick]

Changes with Apache 2.3.0

*) ap_get_server_versi­on() has been removed. Third-party modules must
now use ap_get_server_banne­r() or ap_get_server_descr­iption().
[Jeff Trawick]

so we'll need to address these.

fwiw, there are lots of changes in 2.2.0 and above that simplay haven't
been incorporated into mod_perl yet, simply for lack of developer tuits.
so, help/patches in this respect most welcome. come on and join
dev@perl.a.o if you're interested :)­
This can be solved by applying the following patch:
But note that this is not a backwards compatible patch.

yeah, we can't bork back compat. but there is a way to maintain compat
between moving APIs via modperl_apache_comp­at.c. right now that file is
empty, but you can see what entries would look like by peeking at old
versions in svn.

I suspect what we'd want would be to hack the map to

o add ap_get_server_banne­r and ap_get_server_descr­iption to the apache
function map and mark them both as mod_perl implemented

o add code to modperl_apache_comp­at.(c|h) to implement stubs for those
routines if not currently defined, or callback to them if defined

o mark ap_get_server_versi­on as mod_perl implemented

o add a stub for ap_get_server_versi­on if not defined with a warning
that the function is deprecated (else issue the callback)

we did a similar workaround for something else, but I forget what it
was. svn history will know, however.

--Geoff
comment 5 answers | Add comment
[OT] Is anyone running Apache on Windows Vista? Steve Hay 14:50:11
 Apologies for a slightly off-topic question, but I've had no response to
an ASF Bugzilla bug report or a question on users@httpd.apache.­org

http://issues.apach­e.org/bugzilla/show_­bug.cgi?id=41611
http://marc.info/?l­=apache-httpd-users&­m=117706082102936&w=­2

so I thought I'd try my luck here.

In short, I can't get Apache httpd running as a service on Windows Vista
(with or without mod_perl), and I'm wondering if others have experienced
the same problem and know how to fix it.

Apache 1.x httpd runs fine in a command prompt (rather than as a
service), so I'm positive it isn't a configuration issue, at least as
far as httpd is concerned.

--
Add comment
Tuesday, 24 April 2007
[Fwd: foundation: r10592 - in /foundation/officer­s: cclas.txt grants.txt] Geoffrey Young 23:49:17
 it seems the Apache::Reload grant has been recorded by the ASF
secretary. when I find the time I'll notify incubator, or figure out
the next step so we can import the code.

--Geoff

-------- Original Message --------
Subject: foundation: r10592 - in /foundation/officer­s: cclas.txt grants.txt
Date: Mon, 26 Mar 2007 14:15:06 -0000
From: jim@apache.org
Reply-To: members@apache.org
To: foundation-cvs@apac­he.org

Author: jim
Date: Mon Mar 26 07:15:04 2007
New Revision: 10592

Log:
Add in:

CCLA for Tomad R
Grant for RDFStore
Grant for Apache::Reload
comment 13 answers | Add comment
[RELEASE CANDIDATE] mod_perl-1.30 RC1 Philippe M. Chiasson 23:49:17
 The mod_perl 1.30 release candidate #1 has arrived. It can be
downloaded here:

http://www.apache.o­rg/~gozer/mp1/mod_pe­rl-1.30-rc1.tar.gz

MD5 : 639e045d782a6671111­46a70b7948dfa
SHA1: 942eaffe4570a9060b3­a0ed7de52ac902d054cb­b

The summary of what has changed since 1.29 are (from Changes):

SECURITY: CVE-2007-1349 (cve.mitre.org)
fix unescaped variable interpolation in Apache::PerlRun
regular expression to prevent regex engine tampering.
reported by Alex Solovey
[Randal L. Schwartz <merlyn@stonehenge.com>, Fred Moyer <fred@redhotpenguin.com>]

Pull in the new Apache-SizeLimit from
http://svn.apache.o­rg/repos/asf/perl/Ap­ache-SizeLimit/trunk­
and obsolete the previous lib/Apache/SizeLimi­t.pm.
[Philip M. Gollucci]

Fix an Apache::(Registry|P­erlRun) bug caused by special characters
in the url [kolya@mail.ru]

Display a more verbose message if Apache.pm can't be loaded
[Geoffrey Young]

Fix incorrect win32 detection in Apache::SizeLimit reported by
Matt Phillips <mphillips@virage.c­om> [Philippe M. Chiasson]

The print-a-scalar-refe­rence feature is now deprecated and documented
as such [Stas]

fix "PerlSetVar Foo 0" so that $r->dir_config('Foo­') returns 0, not undef
[Geoffrey Young]

for some reason .pm files during the modperl build see $ENV{PERL5LIB}
set in Makefile.PL, which is used for generating Makefiles, as
"PERL5LIB=/path:/an­other/path" instead of "/path:/another/pat­h"
essentially rendering this env var useless. I'm not sure why, may be
MakeMaker kicks in somewhere. Trying to workaround by
s/PERL5LIB/PERL5LIB­_ENV/, using anything that's not PERL5LIB. [Stas]

change $INC{$key} = undef; to delete $INC{$key}; in PerlFreshRestart
[Geoffrey Young]

Fix a bug in Makefile.PL for Win32 where it would, in
certain cases, pick up the wrong Perl include directory
[Steve Hay]

-------------------­--------------------­--------------------­-------------
Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectopl­asm.org/ m/gozer\@(apache|cp­an|ectoplasm)\.org/
comment 14 answers | Add comment

Add new topic:

How:  Register )
 
Login:   Password:   
Comments by: Premoderation:
Topic:
  
 
Пожалуйста, относитесь к собеседникам уважительно, не используйте нецензурные слова, не злоупотребляйте заглавными буквами, не публикуйте рекламу и объявления о купле/продаже, а также материалы нарушающие сетевой этикет или законы РФ. Ваш ip-адрес записывается.


QAIX > Apache HTTP ServerGo to page: « previous | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | next »

see also:
Unable to install perl 5.6.1 under AIX…
Why could Perl help the PDA enthusiast?
Fw: Modifying directory permission
pass tests:
see also:

  Copyright © 2001—2010 QAIX
Идея: Монашёв Михаил.
Авторами текстов, изображений и видео, размещённых на этой странице, являются пользователи сайта.
See Help and FAQ in the community support.qaix.com.
Write in the community about the bugs you have noticedbugs.qaix.com.
Write your offers and comments in the communities suggest.qaix.com.
Information for parents.
Пишите нам на .
If you would like to report an abuse of our service, such as a spam message, please .
Если Вы хотите пожаловаться на содержимое этой страницы, пожалуйста .