[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#926631: Error HTTP 403 on several deb packages through apt-cacher-ng



Hallo,
* Julian Andres Klode [Tue, Apr 16 2019, 08:05:46AM]:
> Control: reassign -1 apt-cacher-ng
>
> On Tue, Apr 16, 2019 at 07:30:56AM +0200, Eduard Bloch wrote:
> > reassign 926631 apt
> > thanks
> >
> > Hallo,
> > * Dan Rozinsky [Mon, Apr 08 2019, 12:22:53PM]:
> > >    Get:29 [29]http://archive.ubuntu.com/ubuntu bionic/main amd64 socat amd64
> >             ^^^^
> > >    1.7.3.2-2ubuntu2 [342 kB]
> > >    Fetched 20.2 MB in 9s (2357 kB/s)
> > >    E: Failed to fetch
> > >    [30]http://dl.bintray.com/rabbitmq/debian/pool/rabbitmq-server/rabbitmq-server_3.6.16-1_all.deb ;
> > >    403  Forbidden [IP: apt-cacher-server 3142]
> > >    E: Unable to fetch some archives, maybe run apt-get update or try with
> > >    --fix-missing?
> > >    and in the /var/log/apt-cacher-ng/apt-cacher.log on the proxy server:
> > >    1554714723|I|7322905|apt-cacher-client|[31]archive.ubuntu.com/ubuntu/pool/main/e/erlang/erlang-base_20.2.2+dfsg-1ubuntu2_amd64.deb
> >                                             ^^^^
> > What are those numbers? Why does your HTTP client send them as part of the Host header?
>
> Well, you inserted them there, they are not in the bug report.

I didn't. mutt did that apparently.

> > This looks more like a bug report for your client, Ubuntu APT?
> >
> > >    1554714723|O|7322917|apt-cacher-client|[32]archive.ubuntu.com/ubuntu/pool/main/e/erlang/erlang-base_20.2.2+dfsg-1ubuntu2_amd64.deb
> > >    1554714724|I|724718|apt-cacher-client|[33]archive.ubuntu.com/ubuntu/pool/main/e/erlang/erlang-asn1_20.2.2+dfsg-1ubuntu2_amd64.deb
> >
> > Yep, pretty sure that string was added to the hostname. Client bug!
>
> Following above, and given that erlang-base was successfully fetched, I disagree with your
> assessment.

Ok, maybe it was not the mutt garbage but it still does not make much
sense. The only reason for 403 I can imagine there is garbage in the URL
specified by the client. OTOH the workaround from user is also weird and
shouldn't solve anything...
Everything is weird in this bug report. I am closing it for now, please
reopen if the problem occurs again.

Regards,
Eduard.


Reply to: