4 ms·
That sounds more like an Apache problem than a Perl problem. It's their mistake and it's not even relevant outside Apache context
by dtech 1y ago
That sounds more like an Apache problem than a Perl problem. It's their mistake and it's not even relevant outside Apache context
- weinzierl 1y agoIt should have been an Apache problem, yes. Not only did it turn out that at least the language negotiation part of content negotiation wasn't the best idea but the way Apache handled it was problematic apart from the pl problem. In the end the Perl community took the issue upon them, so historically I'd say it was a Perl problem (of choice).
- maxloh 1y agoThat should be marked as a breaking change on Apache side IMO. It would be a security nightmare if server code were leaked to public.