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

Bug#786409: ftp.debian.org: webdir http://ftp-master.debian.org/new/ not accessible any more



Package: ftp.debian.org
Severity: normal

Hi ftpmasters,

I discussed the issue at Debian QA list since it affects an UDD importer
(ftpnew).  Since the assumption came up that the problem is not created
intentionally I'm filing a bug report:

I noticed that the ftpnew gatherer for UDD is currently broken.  The
reason is that it is usually fetching files via

   wget -q -r -N --level=2 --no-parent --no-directories http://ftp-master.debian.org/new/

but if you try

   wget http://ftp-master.debian.org/new/
--2015-05-21 09:19:52--  http://ftp-master.debian.org/new/
Resolving ftp-master.debian.org (ftp-master.debian.org)... 138.16.160.12
Connecting to ftp-master.debian.org (ftp-master.debian.org)|138.16.160.12|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://ftp-master.debian.org/new/ [following]
--2015-05-21 09:19:52--  https://ftp-master.debian.org/new/
Connecting to ftp-master.debian.org (ftp-master.debian.org)|138.16.160.12|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2015-05-21 09:19:53 ERROR 403: Forbidden.

It seems it is forbidden to read the web dir directly.

Paul Wise assumed[1] that this is fallout from the recent upgrade of
franck to jessie and thus suggested to file a bug report.

I can also confirm that I implemented a workaround for UDD which does
not rely on reading the webdir[2].  So the new importer is functional
again and I'd be fine if you simply close this bug in case it was an
intentional configuration change.  Please note that there might be other
applications broken.

In addition Paul suggested another feature[3] to provide all needed data
in .822 format.  I think we discussed this previously and I vaguely
remember that I suggested a patch but it might be lost in eternal byte
space.  If you consider it sensible I'd volunteer to open another bug
about this issue.

Kind regards

        Andreas.

[1] https://lists.debian.org/debian-qa/2015/05/msg00033.html
[2] https://lists.debian.org/debian-qa/2015/05/msg00037.html
[3] https://lists.debian.org/debian-qa/2015/05/msg00038.html


Reply to: