ANNOUNCE: Mod_python 3.3.0b (Beta)

2006-12-25 Thread Gregory (Grisha) Trubetskoy


The Apache Software Foundation and The Apache HTTP Server Project are
pleased to announce the 3.3.0b (Beta) release of mod_python.

Version 3.3.0b of mod_python features several new functions and
attributes providing better access to apache internals, as well as
many bug fixes and various performance and security improvements. A
detailed description of the changes is available in Appendix A of the
mod_python manual, also available here

http://www.modpython.org/live/mod_python-3.3.0b/doc-html/app-changes-from-3.2.10.html

Beta releases are NOT considered stable and usually contain bugs.

This release is intended to solicit widespread testing of the code. We
strongly recommend that you try out your existing applications and
experiment with new features in a non-production environment using
this version and report any problems you may encounter so that they
can be addressed before the final release.

Preferred method of reporting problems is the mod_python user list
[EMAIL PROTECTED]

Mod_python 3.3.0b is available for download from:

http://httpd.apache.org/modules/python-download.cgi

For more information about mod_python visit http://www.modpython.org/

Regards,

The Apache mod_python team.




Re: [EMAIL PROTECTED] ANN: mod_proxy_html 3.0-dev

2006-12-25 Thread Jens Schleusener
Hi,

On Mon, 25 Dec 2006, Nick Kew wrote:

 I've made a number of significant updates to mod_proxy_html,
 and it's working fine for me in a range of tests.
 I'd now like to invite testing and feedback from developers
 and bleeding edge users.
 
 The major new features in mod_proxy_html 3.0 are inspired
 by the common requests I've had from users of versions 2.x:
 
  * Much improved internationalisation/charset support.
It now works properly with charsets not supported by
libxml2, such as the windows-125x range, and enables
an administrator to correct for backends that fail to
supply the information.  It can also generate output
using any encoding available on the host system.
  * Configurable definition for the set of HTML attributes
to treat as links and events.  So you can now support
rewriting proprietary hacks like td background by
declaring them in httpd.conf.
  * Supports various fixups for bogus and deprecated HTML.
  * Supports flexible configuration, through interpolating
environment variables in ProxyHTMLURLMap rules, and
supports conditional processing of individual rules.
 
 Other feature requests can still be considered, too!
 
 The next task is to update the documentation further,
 notably the tutorial.  The recipes everyone seems to
 copy were designed for Apache 2.0 and mod_proxy_html 1.x,
 and while they work for later versions, they lead users
 into some gotchas in spite of my warnings!
 
 http://apache.webthing.com/mod_proxy_html/
 
 -- 
 Nick Kew

Thanks for the good (christmassy) news. 

But installing 3.0-dev revision 76 and adding in httpd.conf 

 LoadFile/usr/lib/libxml2.so
 LoadModule  proxy_html_modulemodules/mod_proxy_html.so
 Include conf/proxy_html.conf

while checking the apache syntax I got the following error

 $ /usr/local/www/httpd2.2.3/bin/apachectl  configtest
 Syntax error on line 22 of /usr/local/www/httpd2.2.3/conf/proxy_html.conf:
 Invalid command 'ProxyHTMLLink', perhaps misspelled or defined by a module 
 not included in the server configuration

Uncommenting the above Include I found via 

 $ /usr/local/www/httpd2.2.3/bin/apachectl -t -D DUMP_MODULES 

the line

 proxy_html_module (shared)

so the corresponding module seems to be loaded correctly.  

Looking in the source code I have the impression that the proxyHTMLLink
declaration lines contains a small typo and must be replaced by 
proxyHTMLLinks. At least the configuration check is thereafter ok.

Greetings

Jens 

-- 
Dr. Jens SchleusenerT-Systems Solutions for Research GmbH
Tel: +49 551 709-2493   Bunsenstr.10
Fax: +49 551 709-2169   D-37073 Goettingen
[EMAIL PROTECTED]  http://www.t-systems.com/


Re: svn commit: r490142 - /httpd/httpd/trunk/modules/mappers/mod_alias.c

2006-12-25 Thread Ruediger Pluem


On 12/25/2006 01:06 PM,  wrote:
 Author: niq
 Date: Mon Dec 25 04:06:33 2006
 New Revision: 490142
 
 URL: http://svn.apache.org/viewvc?view=revrev=490142
 Log:
 PR#35314: Enable path components in Redirect
 
 Modified:
 httpd/httpd/trunk/modules/mappers/mod_alias.c
 
 Modified: httpd/httpd/trunk/modules/mappers/mod_alias.c
 URL: 
 http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/mappers/mod_alias.c?view=diffrev=490142r1=490141r2=490142
 ==
 --- httpd/httpd/trunk/modules/mappers/mod_alias.c (original)
 +++ httpd/httpd/trunk/modules/mappers/mod_alias.c Mon Dec 25 04:06:33 2006
 @@ -204,7 +204,10 @@
  if (ap_is_HTTP_REDIRECT(status)) {
  if (!url)
  return URL to redirect to is missing;
 -if (!use_regex  !ap_is_url(url))
 +/* PR#35314: we can allow path components here;
 + * they get correctly resolved to full URLs.

Where? A quick check shows that the resulting Location header has no scheme and 
host in front.
AFAICT this violates 14.30 of RFC2616 as the value of a Location header must be 
an absoluteURI
or better absolute-URI as defined in 4.3 of RFC3986.
Of course you can already create invalid Location headers with RedirectMatch. 
So it might make
sense to check the validity of a Location header after applying a 
Redirect(Match) to a request
to ensure that it results in an absolute-URI and maybe fix it if it does not 
seem to be one.

Regards

RĂ¼diger


Re: svn commit: r490142 - /httpd/httpd/trunk/modules/mappers/mod_alias.c

2006-12-25 Thread Nick Kew

On 25 Dec 2006, at 22:59, Ruediger Pluem wrote:




-if (!use_regex  !ap_is_url(url))
+/* PR#35314: we can allow path components here;
+ * they get correctly resolved to full URLs.


Where? A quick check shows that the resulting Location header has  
no scheme and host in front.
AFAICT this violates 14.30 of RFC2616 as the value of a Location  
header must be an absoluteURI

or better absolute-URI as defined in 4.3 of RFC3986.


What kind of a quick check?  I ran a case with leading slash, both from
httpd.conf and .htaccess, expecting to see broken Location headers which
I was then going to fix at the point where they're generated (which  
can't

be at config-time because we don't always have a server name at
that point).  But it returned full, valid and correct Location headers
to the client without me doing anything.  Hence the trivial change
and comment.

Of course you can already create invalid Location headers with  
RedirectMatch. So it might make
sense to check the validity of a Location header after applying a  
Redirect(Match) to a request
to ensure that it results in an absolute-URI and maybe fix it if it  
does not seem to be one.


I guessed a fix for that was responsible for the correct headers I saw.

--
Nick Kew


Re: svn commit: r462696 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_disk_cache.c modules/cache/mod_disk_cache.h

2006-12-25 Thread William A. Rowe, Jr.
Just so folks are aware why...

  +APU_DECLARE_DATA const apr_bucket_type_t bucket_type_diskcache = {
  +DISKCACHE, 5, APR_BUCKET_DATA,
  +diskcache_bucket_destroy,
  +diskcache_bucket_read,
  +diskcache_bucket_setaside,
  +apr_bucket_shared_split,
  +apr_bucket_shared_copy
  +};

results in...

 .\mod_disk_cache.c(251) : error C2491: 'bucket_type_diskcache' :
 definition of dllimport data not allowed

...the APU_DECLARE_DATA means This exported data symbol is provided by
APR-UTIL.

APR-UTIL does not include the source mod_disk_cache.c.

Ergo - fubar.




Re: svn commit: r462696 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_disk_cache.c modules/cache/mod_disk_cache.h

2006-12-25 Thread Justin Erenkrantz

On 12/25/06, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:

Just so folks are aware why...

  +APU_DECLARE_DATA const apr_bucket_type_t bucket_type_diskcache = {
  +DISKCACHE, 5, APR_BUCKET_DATA,
  +diskcache_bucket_destroy,
  +diskcache_bucket_read,
  +diskcache_bucket_setaside,
  +apr_bucket_shared_split,
  +apr_bucket_shared_copy
  +};

results in...

 .\mod_disk_cache.c(251) : error C2491: 'bucket_type_diskcache' :
 definition of dllimport data not allowed

...the APU_DECLARE_DATA means This exported data symbol is provided by
APR-UTIL.

APR-UTIL does not include the source mod_disk_cache.c.

Ergo - fubar.


FWIW, I tried CACHE_DECLARE_DATA too and it made no difference.  -- justin