| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 404 on message-ID with slashes |
| Date: | 2021-01-15 16:39:50 |
| Message-ID: | 20210115163950.GA29230@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 2021-Jan-15, Magnus Hagander wrote:
> Some more digging shows the problem does not appear to be the /, but the //.
Hmm ... is it possible that Python somehow interprets the // as a
regex-close marker or escape character or something like that?
> The weird thing is that it works fine in my local dev. Something very
> fishy is afoot here :)
If the Python/django versions are different, maybe there was a bugfix in
between?
--
Álvaro Herrera Valdivia, Chile
"Some men are heterosexual, and some are bisexual, and some
men don't think about sex at all... they become lawyers" (Woody Allen)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-01-15 16:40:42 | Re: 404 on message-ID with slashes |
| Previous Message | Magnus Hagander | 2021-01-15 16:36:42 | Re: 404 on message-ID with slashes |