is that Apache's compat modules are a great solution
and I hoped more projects would use this approach.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
On 2015-06-17 18:03, Helmut K. C. Tessarek wrote:
Hello,
http://httpd.apache.org/docs/2.4/mod/mod_authn_socache.html
There are 2 things I want to mention:
1) cacheing is not a word. It should be replaced with caching on the entire
page
2) AuthnCacheSOCache Directive: If not set, your
.
A default value is not something that is normaly chosen, and if it is, it
should be at least explained how.
What about my 1st item? Misspelling of caching? How to fix it, who can fix it?
Can I clone a repo
and create a pull request or do I have do work with svn?
--
regards Helmut K. C. Tessarek
?
So in case of an authentication module that uses database queries, all
subsequent requests
will still generate SQL statements for the user/group matching. Which means
that only half
of the database requests are actually cached.
Can someone please elaborate.
Cheers,
K. C.
--
regards Helmut K
whatsoever what the platforms' defaults actually are.
Can someone please tell me what the platforms' defaults are?
I'm mostly interested in Linux and MacOSX, but a list would be nice in the docs.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
.
Is there something like that? Are there any examples?
Maybe this is off topic here, but I'd appreciate any pointers.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee
while in reality they are not.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
or other hashes,
if there was as sha-256 hash available. Even on legacy systems I've seen
implementations for sha256.
Thanks again for your answer.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for ch
t part () to indicate the master connection.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
s functionality removed in new protocols?
> As far as I understand renegotiation has (and definitely had in the
> past) serious security issues. Hence it is removed.
Ok, just out of curiosity: was the design flawed or the implementation?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
l
lease shed some light on this?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
On 2016-11-21 12:40, Helmut K. C. Tessarek wrote:
> Can someone please shed some light on this?
Anyone? I really hoped that somebody who knew the code could explain
this behavior to me, since it makes no sense (and contradicts the
documentation).
Cheers,
K. C.
--
regards Helmut K
I'm using them in my
virtual server context, but now I want it to work in the directory
context as well. It is in the documentation after all.
But it is not working and I would like to know why.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0
ing to the
documentation.
But you also mentioned that this scenario won't work with TLS 1.3. Does
this mean you can only have either an auth schema (user/password auth)
or a client cert with TLS 1.3, but not both at the same time? Since when
is functionality removed in new protocols?
Cheers,
K. C.
my point actually. Fixing the design makes no sense, if the
implementation sucks. It's not the first time though that just all
implementations are at a fault. That's why I asked, I just didn't know.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net fo
After upgrading to 2.4.25, I get ERR_SPDY_PROTOCOL_ERROR on several
subdomains and even for Aliases within one domain.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
server. I had
to make it work asap.
I just wanted to mention that there's something off with h2.
Since I only upgraded httpd from 2.4.23 to 2.5.25 w/o changing any
configuration files, it must be a problem with the current h2
implementation.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
ould try to create a few dummy sub domains and see if
it happens again. But I still need info how to debug this any further.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
log should then give an idea of what is going on. Thanks.
Ok, let me create a few dummy subdomains. Hopefully the problem is
reproducible and I can get you the data you need.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
built.)
There are a few options to fix this, but I don't know how you want to
handle this.
Since you work with the build system every day, I'm sure you know the
best way to implement a fix.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
at include)
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
the
best way to implement a fix.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madnessawait
thee at its end.
*/
yway, I'm getting off-topic here...
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
inimized. Yet
I believe it is too dangerous for the average Joe.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
any answers. I'm more into IM.
I've noticed that people on IM are more responsive, since they really
seem to be online when the status says they are online.
Anyway, I don't think that real time chat is necessary, at least not
right away.
--
regards Helmut K. C. Tessarek
lookup https://sks-keyse
On 2017-07-11 08:55, David Zuelke wrote:
> That PHP bug affects parsing of PHP-FPM's config file. It has nothing
> to do with the FastCGI interface or its runtime behavior.
Nope, it also fixed a web application for me.
see https://github.com/nextcloud/server/issues/5660
--
regards Helmu
and prefork.
--
regards Helmut K. C. Tessarek
lookup https://sks-keyservers.net/i for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
before, in a perfect world I'd agree. But this option was
available with FastCgiExternalServer, thus it should be available with
proxy_fcgi as well, especially when proxy_fcgi is the preferred way for
Apache >= 2.4.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup https://sks-keyservers.net/i fo
nextcloud:
https://github.com/nextcloud/server/issues/5660
It didn't help with the rewrite issue.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos an
s sounds more like a bug, because it really shouldn't.
I used rewrite with mod_php. It worked.
Then I switched to mod_proxy_fcgi. Now it does not.
So why is that? I also mentioned I have to debug it further.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerpri
s back.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
ase, yet the bahaviour is different. Don't get me
wrong, but it shouldn't behave differently.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
On 2017-07-21 15:28, Stefan Pernar wrote:
> Thanks everyone. Got it done with nodejs, express and http-proxy.
You know, it is utterly useless to say you have fixed it without telling
people how you did it.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerpr
ink the
implementation. Maybe there should be a way to communicate between fcgi
backed and proxy, so that the request is not lost but sent on a previous
established connection.
This setting should improve performance, not make it possible to have
failed requests due to timeouts and/or hangs.
--
regards Helmut K
request was lost.
(due to timeout, not processing it, or for whatever reason)
It did not mess up the content of the request, if that's what you're
thinking.
The request just did not get through. After removing the Proxy section
with the enablereuse option, all was good again.
--
regards Helmu
chitecture for
> proxied responses in general.
I'm not familiar with that particular code, but would be interested in
looking into it. Does anybody volunteer as a mentor?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup https://sks-keyservers.net/i for KeyID 0xC11F128D
/*
Thou shalt
sts to use
mod_proxy_fcgi, but if above is true, this might lead to problems.
What is your take on this?
--
regards Helmut K. C. Tessarek
lookup https://sks-keyservers.net/i for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
ss it won't be for
a while (timeframe maybe even years?).
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
tter than the younger generation favouring nginx
over Apache because of alleged better out of the box performance.
I'm not sure, how much perf difference there is between A, B, and C, but
SSL by itself has quite an impact, especially on boxes without the AES
CPU extension.
Cheers,
K. C.
--
3 or 4 patch level jump).
Why not tagging an RC? People test the RC. When all is ok, the RC is
released. If not a new RC is tagged.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Tho
ated when mpm is
prefork. Stefan added this in 2.4.27.
There is no h2 with prefork anymore.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer
rocess. The rest will follow.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
edentials.
e.g. with git and a PR concept, there's no need to have login
credentials (but CI can still be used)
Anyway, I'm done. You are either not reading my mails in context or
ignoring what I'm writing. Like the process this conversation is too
tedious for me.
--
regards Helmut K. C.
s quite common, especially if it is a one time
contribution.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
because of them.
I did not suggest to replace your precious work flow, I only showed up
why people _might_ be put off by it.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow
hosts with the same hostname and port.
So why is it necessary to create another unique id?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for
Or at least one that can be used from a combination of several fields in
the server struct.
What am I missing?
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for
nately this output is useless unless you know the revision
numbers by hart. It looks like it is a 2.2 version, but I could be
wrong. (A 2.4 version has a revision around 1826891.)
Note to devs: it would be great, if ab could use the same version
numbers as the server. ;-)
Cheers,
K. C.
--
regards Hel
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/.*
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [QSA,L,R=301]
ServerName HOSTNAME:443
# Your "real" configuration here
Can you please elaborate on your above statement and clear that
On 2019-09-27 10:40, William A Rowe Jr wrote:
> This answer \V/ (from Stefan) below. More explanation follows...
Thanks Bill, your explanation certainly helped to shed some light on this.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerpr
")
In fact a web search does not yield any useful results. Furthermore the OP
most likely meant "what incentive would be required to add it".
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386
If the protocol evolves
so must the server, otherwise the server will be obsolete at one point in the
future.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NUL
re's a good chance someone is as well. Feel free to include my message,
> too.
Yep, this was not on purpose. The httpd mailing list does not provide a
reply-to: header using the mailing list's address. So this can happen.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fi
er out there that can do HTTP/3, people will just use that
one instead. All the excuses (even though I do understand how valid they are)
won't change a thing.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A
On 2021-10-01 10:40, ste...@eissing.org wrote:
> https://dist.apache.org/repos/dist/dev/httpd/
Hmm, something is off. I can see the .htaccess file in the directory listing.
I suspect a directive is missing in the config.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek Ke
someone has seen this as well, in which case you have at least the
info that someone else experiences this also. It has happened about 30 times
in the last 4 hours. It's intermittent and makes no sense.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key
and then due to maybe a race
condition? This his highly speculative of course.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
ctly fine. I don't get any errors and the performance is
subjectively better. Thus I will stick with that version for now.
I will be heading to bed soon. It's rather late (or early) already in EST. ;-)
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key finge
I've setup a test VM and was able to reproduce the problem. However, in my
test I got only one 500 error, but I do have an access log and an error_log
set to http2:debug.
Do you want the 2 logs or is Andreas' log sufficient?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
as an ErrorDocument that sends an email when encountering
a 500.
Thus this 500 is not only in the logs but must also trigger the ErrorDocument
500. Those are also gone now.
Thanks a bunch for fixing this.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint
hine:
In that case the module wouldn't work on Linux either, since the '/tmp/...'
path is hard-coded and /tmp is usually not a tmpfs.
Just my 2 cents.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D
/*
Thou shalt not follow the NULL pointer fo
61 matches
Mail list logo
