Re: svn:eol-style for autoconf stuff
Bill, Am 15.02.2011 00:14, schrieb William A. Rowe Jr.: The answer is to use the correct tool on the correct platform, not to break the line endings for everyone vainly attempting to maintain the files in the text editors of the other platforms. please elaborate who are those 'everyone' folks, and what is the correct platform?? configure & friends are shell scripts - thus every platform which deals with shell scripts should also provide an editor which can edit them, no? what I talk about here mainly is windows, and I guess you know well about the situation on that platform ... If you are foolish enough to mix vc ports of svn with cyg, or visa versa, you have what is coming to you :) yeah, and since there's nowhere a MSYS SVN binary which would do it 'right' I would have to either use Cygwin then, or cant work directly from svn, but need to always do a 'svn export --native-eol LF' in order to get the configure scripts in 'right' format ... so please tell me exactly which platforms may be harmed by 'svn:eol-style LF' for the configure scripts; and please dont tell me now that you allways want to maintain these scripts from a windows box with notepad - then I will reply that you should use the 'right' editor which can handle LF files ... :-) Please see that I want to find a solution which works for most users with the stuff commonly available - and there are a couple of editors available which can handle LF files properly on windows, but so far I have not found a MSYS version of svn, and Cygwin seems a bit overkill just for getting svn only ... Gün.
Re: svn commit: r1070075 - in /httpd/httpd/trunk: CHANGES modules/cache/cache_util.c
On 14 Feb 2011, at 9:22 AM, Ruediger Pluem wrote: What happens if str is supplied as "a, b"? I mean why token + 1 and not token? I guess it's because we know *token isn't a separator, so there is no point checking if it is one a second time. *token might not be a separator, but it might be ". Sorry - I thought you were highlighting the comma and space, rather than the quotes around it. You're right, the +1 does skip an opening quote, which is wrong. It's fixed in r1070699. Regards, Graham --
Re: svn:eol-style for autoconf stuff
On 2/14/2011 5:03 PM, Guenter Knauf wrote: > Hi, > if you checkout apr/apu/httpd from Windows platform you might end up with > buildconf + > configure + friends with CRLF format due the fact that these are marked > 'svn:eol-style > native' ... > see also BZ #46175 > > since these are shell scripts I believe they always need LF line endings > regardless of the > platform, or? > If so I would like to change the svn:eol-style for these files to LF so that > the get > checked out in the right format ... > > please some comments on that! F.e. how about MacOSX? The answer is to use the correct tool on the correct platform, not to break the line endings for everyone vainly attempting to maintain the files in the text editors of the other platforms. If you are foolish enough to mix vc ports of svn with cyg, or visa versa, you have what is coming to you :)
svn:eol-style for autoconf stuff
Hi, if you checkout apr/apu/httpd from Windows platform you might end up with buildconf + configure + friends with CRLF format due the fact that these are marked 'svn:eol-style native' ... see also BZ #46175 since these are shell scripts I believe they always need LF line endings regardless of the platform, or? If so I would like to change the svn:eol-style for these files to LF so that the get checked out in the right format ... please some comments on that! F.e. how about MacOSX? Gün.
Re: Time to start planning for httpd 2.3.11-BETA ?
On 2/14/2011 12:21 PM, Nick Kew wrote: > On Mon, 14 Feb 2011 09:20:49 -0800 > "Gregg L. Smith" wrote: > >> Hi folks, >> >> In the spirit of beta, could we get the last missing module that I know of, >> mod_authn_socache, in the Windows build? Reading it's doc it sounds like a >> good module to have if using dbd for authentication. > > Should be a useful module for dbd-authn users on any platform! > But I don't have a windows platform to test on. I'm happy to do this, or review this if someone has beaten me to it before Wednesday.
Re: Time to start planning for httpd 2.3.11-BETA ?
On 2/12/2011 10:14 AM, Stefan Fritsch wrote: > On Thursday 10 February 2011, Jim Jagielski wrote: >> Let's commit to pushing for a 2.3.11-BETA... > > +1 > > One question: How do we handle truly experimental modules (e.g. > mpm_simple, mod_serf). Move them into an experimental subdir before > branching or branch first and then move stuff around? Or just mark > them as experimental in the docs and maybe in configure? IMHO, all 'experiments' should be provided in all alpha and beta tarballs (disabled by default, obviously). When 2.4 is forked, these can be cast out of the tarball and provided separately until they have the support of the developers. It seems too many legitimate bits have been left in the dumpster of experimental for too long in the past, and having a clear 'promote before GA' policy would help recruit eyeballs to elevate them to code with oversight. WDYAT?
Re: svn commit: r1070660 - /httpd/httpd/trunk/server/config.c
>> + "ensure it is readable and that '%d' " > > %s thanks, already making it's way across the net :)
Re: svn commit: r1070660 - /httpd/httpd/trunk/server/config.c
On Mon, Feb 14, 2011 at 3:49 PM, wrote:
> Author: covener
> Date: Mon Feb 14 20:49:56 2011
> New Revision: 1070660
>
> URL: http://svn.apache.org/viewvc?rev=1070660&view=rev
> Log:
> Log a hint about the directory needing to be executable
> when we hit EACCESS searching for htaccess files.
>
> Modified:
> httpd/httpd/trunk/server/config.c
>
> Modified: httpd/httpd/trunk/server/config.c
> URL:
> http://svn.apache.org/viewvc/httpd/httpd/trunk/server/config.c?rev=1070660&r1=1070659&r2=1070660&view=diff
> ==
> --- httpd/httpd/trunk/server/config.c (original)
> +++ httpd/httpd/trunk/server/config.c Mon Feb 14 20:49:56 2011
> @@ -2034,8 +2034,9 @@ AP_CORE_DECLARE(int) ap_parse_htaccess(a
> && !APR_STATUS_IS_ENOTDIR(status)) {
> ap_log_rerror(APLOG_MARK, APLOG_CRIT, status, r,
> "%s pcfg_openfile: unable to check htaccess
> file, "
> - "ensure it is readable",
> - filename);
> + "ensure it is readable and that '%d' "
%s
> + "is executable",
> + filename, d);
> apr_table_setn(r->notes, "error-notes",
> "Server unable to read htaccess file, denying "
> "access to be safe");
Re: Time to start planning for httpd 2.3.11-BETA ?
On Mon, 14 Feb 2011 09:20:49 -0800 "Gregg L. Smith" wrote: > Hi folks, > > In the spirit of beta, could we get the last missing module that I know of, > mod_authn_socache, in the Windows build? Reading it's doc it sounds like a > good module to have if using dbd for authentication. Should be a useful module for dbd-authn users on any platform! But I don't have a windows platform to test on. > It currently crashes if loaded without any configuration in Windows, it may > even crash with configuration for all I know but I do not have a setup to use > to configure it for at the moment. When does it crash? At startup, or when processing requests? Are you in a position to send any diagnostic information like a traceback that could help us find a bug? Are you running any other modules that use socache? -- Nick Kew Available for work, contract or permanent. http://www.webthing.com/~nick/cv.html
Re: Time to start planning for httpd 2.3.11-BETA ?
Thx! I'm not a Windows user so any info/update/patches are extremely welcome! On Feb 14, 2011, at 12:20 PM, Gregg L. Smith wrote: > Hi folks, > > In the spirit of beta, could we get the last missing module that I know of, > mod_authn_socache, in the Windows build? Reading it's doc it sounds like a > good module to have if using dbd for authentication. > > It currently crashes if loaded without any configuration in Windows, it may > even crash with configuration for all I know but I do not have a setup to use > to configure it for at the moment. > > So if there are no objections I'd like to have it added. > > Regards, > > Gregg > > > -Original Message- > From: Jim Jagielski > To: dev@httpd.apache.org > Date: Thu, 10 Feb 2011 09:27:32 -0500 > Subject: Time to start planning for httpd 2.3.11-BETA ? > > Let's commit to pushing for a 2.3.11-BETA... > > > > > > > > >
Re: Time to start planning for httpd 2.3.11-BETA ?
Hello again, This get's our httpd.conf file in Windows up to date with what is actually being put on the file system with respect to modules. Applies with offset -1 if applied before mod_authn_socache addition in my prior email. Regards, Gregg -Original Message- From: Jim Jagielski To: dev@httpd.apache.org Date: Thu, 10 Feb 2011 09:27:32 -0500 Subject: Time to start planning for httpd 2.3.11-BETA ? Let's commit to pushing for a 2.3.11-BETA... awk_full_module_list.diff Description: Binary data
Re: Time to start planning for httpd 2.3.11-BETA ?
Hi folks, In the spirit of beta, could we get the last missing module that I know of, mod_authn_socache, in the Windows build? Reading it's doc it sounds like a good module to have if using dbd for authentication. It currently crashes if loaded without any configuration in Windows, it may even crash with configuration for all I know but I do not have a setup to use to configure it for at the moment. So if there are no objections I'd like to have it added. Regards, Gregg -Original Message- From: Jim Jagielski To: dev@httpd.apache.org Date: Thu, 10 Feb 2011 09:27:32 -0500 Subject: Time to start planning for httpd 2.3.11-BETA ? Let's commit to pushing for a 2.3.11-BETA... mod_authn_socache_winbuild .diff Description: Binary data
Re: [users@httpd] [mod_ftp] accessing root path with firefox
Am 13.02.2011 23:17, schrieb Carsten Wiedmann: Just some more Infos on this. In my "httpd.conf" I have: | AddHandler cgi-script .pl .php My "ftpd.conf" is: | | DocumentRoot "C:/Users/Public/Downloads" | FTP On | | | | ForceType None | SetHandler None | | | | Now if I try to access "ftp://localhost/perlinfo.pl";, I get this in "ftp_error.log": | [Sun Feb 13 22:59:22 2011] [error] [client 127.0.0.1] \ | Options ExecCGI is off in this directory: \ | C:/Users/Public/Downloads/perlinfo.pl Ok, If I change my "httpd.conf" (and other "AddHandler") to: | | SetHandler cgi-script | it's working. But I still think it should also work with AddHandler. In addition, instead of | | ForceType None | SetHandler None | I now using: | | ForceType None | SetHandler None | because I also don't want thinks like "ftp://localhost/server-info"; are working. BTW: Why is there no "SetOutputFilter None"? At the moment, every time I download a .shtml file through ftp, I get a [warn] in my "ftp_error.log". It would also be nice to have something like "IndexIgnore" for mod_ftp. Regards, Carsten
Re: svn commit: r1070179 - in /httpd/httpd/trunk: CHANGES docs/manual/mod/mod_cache.xml modules/cache/cache_storage.c modules/cache/cache_storage.h modules/cache/mod_cache.c modules/cache/mod_cache.h
On Feb 13, 2011, at 5:03 AM, Graham Leggett wrote: > On 13 Feb 2011, at 9:59 AM, Roy T. Fielding wrote: > >>> URL: http://svn.apache.org/viewvc?rev=1070179&view=rev >>> Log: >>> mod_cache: When a request other than GET or HEAD arrives, we must >>> invalidate existing cache entities as per RFC2616 13.10. PR 15868. >> >> Cache entries should not be invalidated unless the response comes >> back as a success (2xx). Likewise, it only applies to methods with >> known write effects (not including TRACE, OPTIONS, PROPFIND, etc.). >> >> This has already been updated in httpbis p6. > > Hmmm... > > So is it right to say that POST, PUT and DELETE should invalidate, while all > others would be left alone? > > Or do we need some kind of mechanism for modules that respond to new methods > to declare those methods as needing to be invalidated or not? Well, I thought I could answer that with a simple link to the drafts, but they just got changed in the wrong direction. It should be implemented as invalidating when the response is 2xx and the method is *not* one of the safe ones (GET, HEAD, OPTIONS, TRACE, PROPFIND, and maybe REPORT). That way, a new extension method would invalidate on success. > Should the cache try and cache any of the other methods, or is cacheability > limited to GET only? It can cache other methods if it knows how to. PROPFIND is probably the only other method worth caching, but its key depends on a bunch of webdav stuff outside the URI. Roy
