Bill Nottingham wrote:
Ian Burrell (ianburrell@xxxxxxxxx) said:
It looks like it redirects with a 302 to
http://fedora.redhat.com/404.html. That is just plain wrong and
should be fixed.
Maybe yum should have some logic to detect HTML error pages and abort
them early.
How do you detect arbitrary content?
The actual server response is like:
for the mirror.pacific.net.au:
===
HTTP/1.1 404 Not Found
Date: Fri, 09 Jun 2006 11:39:32 GMT
Server: Apache/2.0.54 (Debian GNU/Linux)
Content-Length: 364
Keep-Alive: timeout=15, max=10000
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
===blah.
and for fedora.redhat.com:
===
HTTP/1.1 404 Not Found
Date: Fri, 09 Jun 2006 11:35:08 GMT
Server: Apache
Last-Modified: Fri, 09 Jun 2006 11:15:37 GMT
ETag: "b7ea0-105b-44895859"
Accept-Ranges: bytes
Content-Length: 4187
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
<html>
.<head>
..<title>Fedora Project, sponsored by Red Hat</title>
..<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
..<link rel="stylesheet" type="text/css" media="print"
href="/css/print.css">
..<style type="text/css" media="screen">
...@import url("/css/layout.css");
===blah.
Note all the stuff in the actual header, especially:
HTTP/1.1 404 Not Found
Throwing away the header that has the correct info in it is what is
going wrong. From what someone said urlgrabber is used in yum ->
shouldn't urlgrabber then return fail if the server is stating html
errors eg 404, no matter how pretty the 404 looks to a human using their
web browser ?
DaveT.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
