Possible patch would be moving the "start" handling from post config to
pre config. That way everything gets easier (we are not establishing
listeners and shut them down again shortly after, not establishing
rotatelogs etc.).
Patch against 2.2 head at
http://people.apache.org/~rjung/patches/httpd-
On 26.07.2009 00:41, Rainer Jung wrote:
> Now the new thing: as I reported before, I was testing rotatelogs, but
> then when you asked about peculiarities I forgot to mention rotatelogs.
>
> And yes: as soon as I throw out rotatelogs, the problem disappears. When
> I add rotatelogs I can reproduce
Still not a complete solution to the puzzle, but some more findings below.
On 25.07.2009 20:55, William A. Rowe, Jr. wrote:
> Rainer Jung wrote:
>> On 25.07.2009 18:36, William A. Rowe, Jr. wrote:
>>> Rainer Jung wrote:
On 25.07.2009 16:05, Rainer Jung wrote:
> 5) Starting a service only
Rainer Jung wrote:
> On 25.07.2009 18:36, William A. Rowe, Jr. wrote:
>> Rainer Jung wrote:
>>> On 25.07.2009 16:05, Rainer Jung wrote:
5) Starting a service only works using the ApacheMonitor or the Windows
Service Control. Using the commandline httpd.exe I can not start the
service
On 25.07.2009 18:57, Rainer Jung wrote:
Oups:
> and 12, so I'll shut down now and come back when I really know the
shut down -> shut up
On 25.07.2009 18:36, William A. Rowe, Jr. wrote:
> Rainer Jung wrote:
>> On 25.07.2009 16:05, Rainer Jung wrote:
>>> 5) Starting a service only works using the ApacheMonitor or the Windows
>>> Service Control. Using the commandline httpd.exe I can not start the
>>> service. The event log shows:
>>>
Rainer Jung wrote:
> On 25.07.2009 16:05, Rainer Jung wrote:
>> 5) Starting a service only works using the ApacheMonitor or the Windows
>> Service Control. Using the commandline httpd.exe I can not start the
>> service. The event log shows:
>>
>> [Sat Jul 25 15:11:03 2009] [notice] Disabled use of
On 25.07.2009 16:05, Rainer Jung wrote:
> 5) Starting a service only works using the ApacheMonitor or the Windows
> Service Control. Using the commandline httpd.exe I can not start the
> service. The event log shows:
>
> [Sat Jul 25 15:11:03 2009] [notice] Disabled use of AcceptEx() WinSock2 API
>
Rainer Jung wrote:
5) Starting a service only works using the ApacheMonitor or the Windows
Service Control. Using the commandline httpd.exe I can not start the
service. The event log shows:
[Sat Jul 25 15:11:03 2009] [notice] Disabled use of AcceptEx() WinSock2 API
(OS 10048)Normalerweise darf
I built and tested on Windows XP SP3. There's no Win source download
available at /dev/dist yet, but I did the build using the Unix sources.
It looks good in principle, so
+1
but I have some observations to remark (all tests done with
Win32DisableAcceptEx). See especially remark number 5).
1) R
Nicholas Sherlock wrote:
Thanks, I wasn't certain if the behaviour I wanted was HTTP-correct, but
it seems that it is (and anyway it'll save me on bandwidth costs, so I
really want to fix it). I'll go add it now.
This is now bug report #47580
https://issues.apache.org/bugzilla/show_bug.cgi?id
Dan Poirier wrote:
Nicholas Sherlock writes:
If you make a conditional request for a cached document, but the
document is expired in the cache, mod_cache currently passes on the
conditional request to the backend. If the backend responds with a
"304 Not Modified" response that indicates that t
Nicholas Sherlock writes:
> If you make a conditional request for a cached document, but the
> document is expired in the cache, mod_cache currently passes on the
> conditional request to the backend. If the backend responds with a
> "304 Not Modified" response that indicates that the cached copy
Hi everyone,
If you make a conditional request for a cached document, but the
document is expired in the cache, mod_cache currently passes on the
conditional request to the backend. If the backend responds with a "304
Not Modified" response that indicates that the cached copy is still up
to d
14 matches
Mail list logo
