MODPYTHON-34 has been fixed in the current version of the publisher,
with the new importing system. As I've written before, I can roll back
the part regarding the import system if you really want that, all the
while maintaining the fix for MODPYTHON-34.
Regards,
Nicolas2005/7/29, Graham Dumpleton
[ http://issues.apache.org/jira/browse/MODPYTHON-59?page=all ]
Nicolas Lehuen updated MODPYTHON-59:
Fix Version: 3.3.0
Version: 3.1.4
3.1.3
3.2.0
(was: 3.3.0)
Add get_session() method
[ http://issues.apache.org/jira/browse/MODPYTHON-65?page=all ]
Nicolas Lehuen resolved MODPYTHON-65:
-
Fix Version: 3.2.0
Resolution: Fixed
3.2 working version will not install on Mac OS X (10.3.7)
Support the HEAD method properly
Key: MODPYTHON-71
URL: http://issues.apache.org/jira/browse/MODPYTHON-71
Project: mod_python
Type: Bug
Versions: 3.1.4, 3.1.3, 2.7.10, 3.2.0
Reporter: Nicolas Lehuen
Priority: Minor
Nicolas Lehuen wrote:
Another remark : has anyone suscribed to redhat, debian etc. mailing
list to watch for such patches ?
Not me.
I don't understand why those guys
aren't posting their patches on the mod_python mailing list.
I was wondering the same thing. What would be better for us,
On Wed, Aug 10, 2005 at 09:04:04AM -0400, Jim Gallacher wrote:
Nicolas Lehuen wrote:
I don't understand why those guys
aren't posting their patches on the mod_python mailing list.
I was wondering the same thing. What would be better for us, subscribing
to a bunch of mailing lists or
Nicolas Lehuen wrote:
MODPYTHON-34 has been fixed in the current version of the publisher,
with the new importing system. As I've written before, I can roll back
the part regarding the import system if you really want that, all the
while maintaining the fix for MODPYTHON-34.
I haven't had
Jim Gallacher wrote:
Interestingly, section 5.1.1 says that The methods GET and HEAD MUST be
supported by all general-purpose servers., so it would seem that
mod_python has not been compliant to the RFC.
FWIW, the Debian Woody package of mod_python (libapache-mod-python
2.7.8-0.0woody5)
Juha-Matti Tapio wrote:
On Wed, Aug 10, 2005 at 09:04:04AM -0400, Jim Gallacher wrote:
Nicolas Lehuen wrote:
Having some contact with them directly is probably a good idea anyway.
Subscribing to a bunch of mailing lists could result in a lot of
uninteresting mail. ;)
I think it would be
I do not have immediate comment on what you're doing, but I do have a
tangential comment:
Never having looked at the mod_python.util.fs_apply_data code, your
email prompted me to. I noticed that the code uses object as a
function argument name. While this works, shouldn't the argument name
be
[
http://issues.apache.org/jira/browse/MODPYTHON-71?page=comments#action_12318388
]
Jim Gallacher commented on MODPYTHON-71:
Apache may already be doing the right thing for us. Using netcat as the client
I ran the some tests using the the
I'd like to stress the fact that a lot of issues currently in JIRA are
related to the publisher. We have worked on it to solve some of these
issues. I have made sure that both the old version and the new version
pass a series of unit tests. I can't be sure that those unit tests
reflect the whole
Nicolas Lehuen wrote:
I'd like to stress the fact that a lot of issues currently in JIRA are
related to the publisher. We have worked on it to solve some of these
issues. I have made sure that both the old version and the new version
pass a series of unit tests. I can't be sure that those unit
[ http://issues.apache.org/jira/browse/MODPYTHON-12?page=all ]
Graham Dumpleton updated MODPYTHON-12:
--
Attachment: package.diff.txt
An even simpler test for this problem is to use a publisher function defined as:
import mod_python
def index(req):
This has been discussed before(*), but I never got around
to patching it in SVN.
(1) ProxyPassReverse is documented as working inside Location
(2) ... but ProxyPassReverse is implemented on the *server* config.
So, although it is syntactically correct within Location due to a
hack, it doesn't
On Tue, Aug 09, 2005 at 10:40:28PM +0100, Colm MacCarthaigh wrote:
mod_setenvif.c:126: error: syntax error before '*' token
mod_setenvif.c:126: warning: data definition has no type or storage class
mod_setenvif.c: In function `match_headers':
mod_setenvif.c:542: error: called object is not a
Parin Shah wrote:
Would there be value in teaching ap_read_request() how to not break if
you called ap_read_request(NULL)?
Well, I couldnt find a way to do this. and with NULL value it crashes.
What I meant was that you modify the ap_read_request() to not crash when
NULL is passed to it.
On Wed, Aug 10, 2005 at 12:54:22AM +0100, Nick Kew wrote:
Looks like a missing declaration for an optional function.
Needs fixing - yes - but where does libssl come in to it?
If I installed libssl-dev, it would compile just fine. But a completely
pristine checkout gets rid of the problem.
On 06/08/2005, at 12:02 AM, Gregory (Grisha) Trubetskoy wrote:
Just thought I'd ask if we're making any progress towards a 3.2
tarball to test. No pressure, just curious :-)
What I would like to know is what is going to happen in respect of the
changes to the module importer for
Hi Graham,
Apart from the fact that it is a third way to import modules, I don't
see any problem with the new importing system, as it fixes a lot of
bugs while not touching anything on the apache.import_module side. We
have agreed, I think, that we should not make
mod_python.publisher.get_page()
I've just been writing an Apache2 module. To help myself with this, I
made a searchable version of the doxygen-generated documentation in
the Apache2 source code.
In case anyone else would find it useful, I've put it up on
http://www.hobthross.com/docs/apache2/srcdoc
Comments welcome
Rachel
Nicolas Lehuen wrote:
Hi Jim,
Do you want me to mark the issues resolved ? Don't you have the rights
to do this ? If you don't have the right, then maybe Scott Sanders can
give them to you (and to Graham while we're at it...). Scott, are you
reading this ?
No, I don't have permissions to
Nicolas,
I should have mentioned that I would like you to mark them as resolved,
but you have anyway, so all is well. :)
Jim
Jim Gallacher wrote:
Nicolas Lehuen wrote:
Hi Jim,
Do you want me to mark the issues resolved ? Don't you have the rights
to do this ? If you don't have the
On Wed, Aug 10, 2005 at 09:00:31PM +1000, Graham Dumpleton wrote:
I guess the question I have is whether it is worthwhile supporting
HEAD in the first place with mod_python.publisher? What does one
actually gain, especially when it will not strictly work in all
situations?
The RFC
Okay. What though are the implications of content still being returned
for a HEAD request. What does the standard say about that?
On 10/08/2005, at 10:01 PM, Juha-Matti Tapio wrote:
On Wed, Aug 10, 2005 at 09:00:31PM +1000, Graham Dumpleton wrote:
I guess the question I have is whether it is
Nicolas Lehuen wrote:
Hi Nicolas,
Could you mark these issues as resolved as well?
Potential deadlock in psp cache.
http://issues.apache.org/jira/browse/MODPYTHON-69
Add configure --with-max-locks option to set MAX_LOCKS.
http://issues.apache.org/jira/browse/MODPYTHON-70
(We can create a new
On Wed, Aug 10, 2005 at 10:08:08PM +1000, Graham Dumpleton wrote:
Okay. What though are the implications of content still being returned
for a HEAD request. What does the standard say about that?
RFC 2616, 9.4 HEAD
The HEAD method is identical to GET except that the server MUST NOT return
[ http://issues.apache.org/jira/browse/MODPYTHON-70?page=all ]
Nicolas Lehuen resolved MODPYTHON-70:
-
Fix Version: 3.2.0
Resolution: Fixed
Add configure --with-max-locks option to set MAX_LOCKS.
Have a strange patch here for consideration.
In CherryPy, one can manually construct the page hierarchy by writing:
cpg.root.onepage = OnePage()
cpg.root.otherpage = OtherPage()
cpg.root.some = Page()
cpg.root.some.page = Page()
The closest equivalent to this in mod_python is the
2005/8/10, Graham Dumpleton [EMAIL PROTECTED]:
Have started to have a look through the latest mod_python.publishercode, got a few comments to make about it.First is that it has been changed to allow HEAD requests whereasbefore it only supported GET and POST. A HEAD request is handled
by the
This is particularly tricky. I don't know how many app server prevent
content from being returned on a HEAD request, but I guess there aren't
too many. However, it's a MUST NOT, so it should be prevented.
Maybe mod_python could replace req.write with a NOP function whenever the request method is
Another remark : has anyone suscribed to redhat, debian etc. mailing
list to watch for such patches ? I don't understand why those guys
aren't posting their patches on the mod_python mailing list.
Regards,
Nicolas2005/8/10, Nicolas Lehuen [EMAIL PROTECTED]:
This is particularly tricky. I don't
Hi,
First pass at updating mod_mbox scripts to use the new mod-mbox-util program;
various other minor updates.
Modified:
httpd/mod_mbox/trunk/scripts/catchup-archive
httpd/mod_mbox/trunk/scripts/create-index
httpd/mod_mbox/trunk/scripts/create-site-index
Rachel Willmer wrote:
I've just been writing an Apache2 module. To help myself with this, I
made a searchable version of the doxygen-generated documentation in
the Apache2 source code.
In case anyone else would find it useful, I've put it up on
http://www.hobthross.com/docs/apache2/srcdoc
Maxime Petazzoni wrote:
Hi,
First pass at updating mod_mbox scripts to use the new mod-mbox-util program;
various other minor updates.
Modified:
httpd/mod_mbox/trunk/scripts/catchup-archive
httpd/mod_mbox/trunk/scripts/create-index
httpd/mod_mbox/trunk/scripts/create-site-index
I must have missed it while away on vacation, but what is
the criteria on what gets in 2.1.x and what gets in 2.3.x.
Does this mean that for stuff to get in 2.2, it needs
to go into 2.3.x (trunk) then get proposed for backport
into 2.1/2.2?
I've never been all that happy with the current setup in having
load balance methods be so hard coded into the proxy module. Adding
another method requires too many changes.
So I've refactored those sections to allow for additional
lb methods to be added via simple submodules.
Prelim Patch is
Jim Jagielski wrote:
I must have missed it while away on vacation, but what is
the criteria on what gets in 2.1.x and what gets in 2.3.x.
Does this mean that for stuff to get in 2.2, it needs
to go into 2.3.x (trunk) then get proposed for backport
into 2.1/2.2?
No.
Don't mess with the 2.2
Paul Querna wrote:
Jim Jagielski wrote:
I must have missed it while away on vacation, but what is
the criteria on what gets in 2.1.x and what gets in 2.3.x.
Does this mean that for stuff to get in 2.2, it needs
to go into 2.3.x (trunk) then get proposed for backport
into 2.1/2.2?
Jim Jagielski wrote:
I've never been all that happy with the current setup in having
load balance methods be so hard coded into the proxy module. Adding
another method requires too many changes.
Right, but mod_proxy_balancer was not meant to be a generic
placeholder for
Jim Jagielski wrote:
Paul Querna wrote:
Jim Jagielski wrote:
I must have missed it while away on vacation, but what is
the criteria on what gets in 2.1.x and what gets in 2.3.x.
Does this mean that for stuff to get in 2.2, it needs
to go into 2.3.x (trunk) then get proposed for backport
into
Paul Querna wrote:
So what does the 'Changes with Apache 2.3.0' and
'Changes with Apache 2.1.7' sections mean?
It means someone changed it while i was vacationing in Europe after
ApacheCon, and that I didn't notice.
:)
--
On Aug 10, 2005, at 11:24 AM, Mladen Turk wrote:
Jim Jagielski wrote:
I've never been all that happy with the current setup in having
load balance methods be so hard coded into the proxy module. Adding
another method requires too many changes.
Right, but mod_proxy_balancer was not meant
Jim Jagielski wrote:
Jim Jagielski wrote:
I don't know what you mean...
Well, IMO if there is a need for a new balancer
one should write a new balancer module.
Right now we have both API and functionality
inside mod_proxy that enables one to do that.
If we start adding hooks to the
Mladen Turk wrote:
Jim Jagielski wrote:
Jim Jagielski wrote:
I don't know what you mean...
Well, IMO if there is a need for a new balancer
one should write a new balancer module.
Not balancer. Method.
Right now we have both API and functionality
inside mod_proxy that enables
Jim Jagielski wrote:
Did you even look at the patch? Your comments show
a supreme lack of understanding what it does.
Look Jim, I'm too old and too tired for such discussions.
If you think your patch will make the Earth a better place
to live on, you have my +1.
In future, please do not
Mladen Turk wrote:
Jim Jagielski wrote:
Did you even look at the patch? Your comments show
a supreme lack of understanding what it does.
Look Jim, I'm too old and too tired for such discussions.
If you think your patch will make the Earth a better place
to live on, you have my
Jim Jagielski wrote:
I wasn't. It was simply that we appeared to be discussing
2 different things.
Bet I'm older and more tired than you are ;)
Right. Ever visited Vukovar?
Anyhow, I think that all balancer methods should be
threated just like a protocols. If you have
a new XXX protocol,
Mladen Turk wrote:
Jim Jagielski wrote:
I wasn't. It was simply that we appeared to be discussing
2 different things.
Bet I'm older and more tired than you are ;)
Right. Ever visited Vukovar?
Got me there :)
Anyhow, I think that all balancer methods should be
threated
Actually, I think they do belong in this repository. We should really
add the CGI script that does the msgid search too. Hopefully, once the
mbox-search project is done, we can replace more of these scripts.
As I said, they are related exclusively to the ASF mailing lists. I did
not even
--On August 10, 2005 7:26:44 AM -0700 Paul Querna [EMAIL PROTECTED]
wrote:
Since most of these scripts (create-site-index in particular) are
dedicated to mail-archives.a.org, I don't believe they belong to the
mod_mbox repository (more in something like the infra repos for
example).
Certainly for simpler setups, you might not want to use these scripts.
But, if you're doing a large setup, it'd greatly easy the difficulty in
setting the archives up if you can build upon a set of scripts that others
have used.
I believe this is why we have package mainteners : to gather
Now that mod_ftp is entering Incubation, if you are interested in
serving on the PPMC, please contact me directly.
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
Sith
--On August 8, 2005 1:25:46 PM +0100 Colm MacCarthaigh [EMAIL PROTECTED]
wrote:
O.k., I've merged our two patches, but I've changed a few things, tell
me if there's anothing you think is wrong;
Would you mind writing up a log message for this patch?
I've lost track of what it's supposed to
--On August 8, 2005 1:58:53 AM +0100 Colm MacCarthaigh [EMAIL PROTECTED]
wrote:
And since nothing says it like code, here's a patch to htcacheclean
which adds a -t option to clean out empty directories.
Thanks! Committed a variant in r231351.
FWIW, I agree with Andreas and Rüdiger. =) --
At 12:07 PM 8/10/2005, Jim Jagielski wrote:
Mladen Turk wrote:
Anyhow, I think that all balancer methods should be
threated just like a protocols. If you have
a new XXX protocol, you will need to add the XXX
proxy protocol handler.
I just feel that being able to add a 'byrandom' method,
The Apache API isn't available to your CGI's - you need to
write an actual module. Those .so's, httpd, apr, etc, are
all dumped when the cgi is forked.
Bill
At 12:09 AM 8/10/2005, Balaji wrote:
Hi All,
I am trying to compile a cgi-bin program and also making use of an
Apache DSO
--On August 8, 2005 1:25:46 PM +0100 Colm MacCarthaigh [EMAIL PROTECTED]
wrote:
O.k., I've merged our two patches, but I've changed a few things, tell
me if there's anothing you think is wrong;
Would you mind writing up a log message for this patch?
I've lost track of what it's supposed to
As far as I can tell, Apache 1.3 still assumes that SO_LINGER is
broken on all OSes. Is SO_LINGER still broken on all OSes? What does
Apache2 do with SO_LINGER? I could not figure it out since all the
documentation (manual and code comments) refer to Aapche 1.3 code.
Things like USE_SO_LINGER,
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2005-08-09 12:14:54 -0400 (Tue, 09 Aug 2005) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
Documentation status is
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Stuff to do:
* finish the t/TEST exit code issue (ORed with 0x2C if
framework failed)
* change existing tests that frob the
APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2005-06-30 16:42:43 -0400 (Thu, 30 Jun 2005) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
Documentation status is maintained
What I meant was that you modify the ap_read_request() to not crash when
NULL is passed to it.
As far as I am aware, the request_req only needs certain fields copied
out of connection_req, not all of which are required.
- I played with it to make it work without conn_rec, but it doesnt
William A. Rowe, Jr. wrote:
At 10:17 AM 8/10/2005, Paul Querna wrote:
Jim Jagielski wrote:
I must have missed it while away on vacation, but what is
the criteria on what gets in 2.1.x and what gets in 2.3.x.
Does this mean that for stuff to get in 2.2, it needs
to go into 2.3.x
65 matches
Mail list logo
