From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 404 on message-ID with slashes |
Date: | 2021-01-15 12:46:10 |
Message-ID: | 210E9768-18CA-490D-AF7E-0CDFB575050E@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> On 15 Jan 2021, at 13:30, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> On Fri, Jan 15, 2021 at 1:25 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>
>> Trying to load the last message in https://commitfest.postgresql.org/31/2858/ I
>> ran into an unexpected 404 which, it seems, is due to a message-id with
>> slashes: X//bJ6HKQJWx1wxA(at)paquier(dot)xyz
>>
>> Is this a known problem?
>
> Alvaro mentioned it yesterday, but that's the first I've heard of it
> (and AFAIK with the exact same message-id). A quick look showed it
> wasn't dead obvious what the problem was, but I haven't had time to
> dig into it anymore. Alvaro disappeared out of the discussion, so I'm
> not sure if he's had time to look anythign more beyond that either.
From a quick skim, RFC 1036 a slash is an allowed (but discouraged) character
in a message-id and the obsoleting RFC (5322) support that. I would expect
message-id generators to avoid using slashes though so I wouldn't be surprised
if it's quite rate.
cheers ./daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Lawrence Barwick | 2021-01-15 13:05:35 | CV/Resume spam mails |
Previous Message | Magnus Hagander | 2021-01-15 12:30:48 | Re: 404 on message-ID with slashes |