Closed stantona closed 6 years ago
@stantona You're probably using the wrong URI in the package.list for the Graylog package repository.
See http://docs.graylog.org/en/2.4/pages/installation/operating_system_packages.html#manual-repository-installation for the correct URI.
We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our discussion forum or join the #graylog channel on freenode IRC.
Thank you!
I'm not sure whether this is the correct repository to file this issue, but this relates to installing
graylog-server
from the Debian sources. After setting up the apt repository according to the documentation, I'm encountering a problem when the repository is updated.After doing a
apt-get update
on Debian 9, I get the following:I notice that requests made to the packages endpoint always seem to result in a 200 result, regardless of whether the file exists. E.g, for
InRelease
(which doesn't exist):For
Release
:The body of the request is HTML with the Graylog header with an empty list of results.
I'm wondering whether these requests are not redirecting as they should? For e.g, should
InRelease
redirect (302) toRelease
, which in turn redirects to the file on S3? Making the request in the browser by following the hyperlinks works this way.