From: | Jared Brogan <jaredbrogan(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-www(at)postgresql(dot)org |
Subject: | Re: Wiki editor request |
Date: | 2023-02-06 22:13:27 |
Message-ID: | CANk56d1Cx=7i1fgkRVCgz8=uj5rX_x=tO+hpaptUDR2P-Z2qZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Yeah, I'm not denying something like that may be happening. I mentioned in
my original message that this does not happen on every system, so if
anything a simple note could be appended to the current doc stating it
could resolve the issue.
If you (and presumably the rest of the wiki admins/contributors) deem this
not necessary, then I will not fight that. Just trying to help the larger
audience.
Thanks,
Jared Brogan
On Mon, Feb 6, 2023 at 4:09 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 2/6/23 13:52, Jared Brogan wrote:
> > Here's the output before changing to https and then afterwards:
> > image.png
> >
>
>
> That looks like DNS issues from Azure to me.
>
> In a browser I can do:
>
> http://72.32.157.246:80/pub/repos/apt/
>
> and get to the repo.
>
> And if in a browser I do:
>
> http://apt.postgresql.org/pub/repos/apt/
>
> I end up at:
>
> https://apt.postgresql.org/pub/repos/apt/
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-02-06 22:34:47 | Re: Wiki editor request |
Previous Message | Adrian Klaver | 2023-02-06 22:09:49 | Re: Wiki editor request |