unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: meta@public-inbox.org
Subject: [PATCH] public-inbox.cgi(1): Mention AllowEncodedSlashes for Apache setups
Date: Fri, 17 Feb 2023 12:08:50 +0100	[thread overview]
Message-ID: <20230217110850.1439844-1-u.kleine-koenig@pengutronix.de> (raw)
In-Reply-To: <20230217102828.M907338@dcvr>

When AllowEncodedSlashes is Off (the default setting), URLs containing
%2f are replied with a 404 error without calling the CGI. To (maybe)
prevent others debugging this issue add a hint with the solution.
---
 Documentation/public-inbox.cgi.pod | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/public-inbox.cgi.pod b/Documentation/public-inbox.cgi.pod
index 71f8a6f5f696..369813d09b91 100644
--- a/Documentation/public-inbox.cgi.pod
+++ b/Documentation/public-inbox.cgi.pod
@@ -16,6 +16,11 @@ CGI with Perl is slow due to code loading overhead and web servers lack
 the scheduling fairness of L<public-inbox-httpd(1)> for handling git
 clones and streaming large mbox downloads.
 
+=head1 COMPATIBILITY NOTE
+
+When using the CGI with Apache, make sure to set AllowEncodedSlashes to On, as
+public-inbox makes heavy use of encoded slashes.
+
 =head1 CONTACT
 
 Feedback welcome via plain-text mail to L<mailto:meta@public-inbox.org>
-- 
2.39.1


  parent reply	other threads:[~2023-02-17 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 21:05 Bug related to (maybe?) / in Message-Id Uwe Kleine-König
2023-02-16 21:36 ` Eric Wong
2023-02-17  8:52   ` Uwe Kleine-König
2023-02-17 10:28     ` Eric Wong
2023-02-17 10:32       ` [PATCH] TODO: handle more cases of unencoded slashes Eric Wong
2023-02-17 11:08       ` Uwe Kleine-König [this message]
2023-02-17 13:15         ` [PATCH] public-inbox.cgi(1): Mention AllowEncodedSlashes for Apache setups Eric Wong
2023-02-18 17:58       ` Bug related to (maybe?) / in Message-Id Thomas Weißschuh
2023-02-18 18:06         ` Thomas Weißschuh
2023-03-07  8:31           ` Eric Wong
2023-03-07 22:30             ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230217110850.1439844-1-u.kleine-koenig@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).