Bug 809730 - [PATCH] Fix compilation with httpd-2.4
Summary: [PATCH] Fix compilation with httpd-2.4
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mod_limitipconn
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-04 08:38 UTC by Jan Kaluža
Modified: 2015-02-18 11:08 UTC (History)
3 users (show)

Fixed In Version: mod_limitipconn-0.23-9.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 11:08:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
proposed patch (1.44 KB, patch)
2012-04-04 08:38 UTC, Jan Kaluža
no flags Details | Diff

Description Jan Kaluža 2012-04-04 08:38:08 UTC
Attached patch fixes compilation with httpd-2.4. I've tested it briefly, but you should test it yourself before using the patch and also inform the upstream.

Comment 1 Jan Kaluža 2012-04-04 08:38:49 UTC
Created attachment 575064 [details]
proposed patch

Comment 2 Matthias Saou 2012-04-04 11:33:28 UTC
Thanks a lot!

One question : Do you really need to hardcode a new default content type, or would it be possible to access the one which is already configured for the server?

Comment 3 Jan Kaluža 2012-04-05 04:53:39 UTC
Well, as I understand it now, there is no default_type just now for httpd, I will try to google it more to be sure...

> ap_default_type()
>     This is no longer available; Content-Type must be configured explicitly or > added by the application.

Note that this patch I sent is only for the compilation problem. You should follow https://fedoraproject.org/wiki/PackagingDrafts/ApacheHTTPModules to convert it properly (I forgot to mention it).

Comment 6 Joe Orton 2012-04-17 12:55:38 UTC
I mailed the patch from -8 upstream, here's my comment on handling absent c-type:

""
In 2.4.x there is no concept of a "default" content-type, so I took the
approach of ignoring the "no limit" list for a resource with no
content-type, and never applying limit checking if an exclusive list is
present and the content-type is absent.  I hope this makes sense.
""

Comment 7 David Jao 2012-04-18 18:16:37 UTC
I am the upstream author. The patch from Jan/Joe seems to work and doesn't break previous httpd versions. I'll release a new upstream in a few days. The delay is just to make sure that no more unexpected problems crop up.

I don't know how old a Fedora version you want to try to support, but on Fedora 14 the following additional compatibility macro is required in order for the package to build:

%{!?_httpd_moddir: %{expand: %%global _httpd_moddir %%{_libdir}/httpd/modules}}

(Fedora 15 and 16 do not need this macro -- I've tested it.) Since the macro does not seem to harm anything on more recent Federa versions, you might consider including it anyway.

Comment 8 Matthias Saou 2012-04-19 08:12:33 UTC
Thanks Joe for fixing this one, and David for confirming!

David : Once the next upstream release is available, I'll go ahead and update the package, and make sure I include the relevant macro lines to have the same spec build fine on older releases such as RHEL5 (apache httpd 2.2.3 without the _httpd_* globals in the build macros).

Comment 10 Joe Orton 2012-04-19 08:46:16 UTC
I addded the _httpd_moddir macro too, thanks David for the review.

Comment 11 David Jao 2012-04-25 23:10:48 UTC
New upstream version: http://dominia.org/djao/limit/mod_limitipconn-0.24.tar.bz2

Comment 12 Fedora End Of Life 2013-04-03 20:27:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 13 Fedora End Of Life 2015-01-09 22:30:34 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2015-02-18 11:08:05 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.