Bug 129217 – Links to GFS whitepaper PDFs are all 404

Bug 129217 - Links to GFS whitepaper PDFs are all 404

Summary:	Links to GFS whitepaper PDFs are all 404

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Web Site
Classification:	Red Hat
Component:	Download (Show other bugs)
Sub Component:
Version:	current
Hardware:	All Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Web Development
QA Contact:	Web Development
Docs Contact:

URL:	http://www.redhat.com/software/rha/gfs/
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-08-05 03:55 EDT by Daniel Berrange
Modified:	2007-04-18 13:10 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-08-09 16:45:11 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Berrange 2004-08-05 03:55:47 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4)
Gecko/20030624 Netscape/7.1 (ax)

Description of problem:
The links at the bottom of the page all (apart from the very last)
return 404 errors:

    * Red Hat Global File System Overview (PDF)
    * Whitepaper: Oracle 9i RAC and the Red Hat Global File System
    * Whitepaper: Data Sharing Clusters for Web Serving and Grid Computing
    * Whitepaper: Creating a Scalable Open Source Storage Architecture



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Go to http://www.redhat.com/software/rha/gfs/
2. Try and download any PDF whitepapers
3.
    

Actual Results:  404

Expected Results:  PDF displayed

Additional info:

Comment 1 Luke Meyer 2004-08-09 16:45:11 EDT

fixed.  thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.