Bug 87791 - how to deal with shutting down the up2date v1 servers
how to deal with shutting down the up2date v1 servers
Status: CLOSED NOTABUG
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Stable
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike Orazi
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-02 10:59 EST by Red Hat Production Operations
Modified: 2008-02-13 16:52 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-13 16:52:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2003-04-02 10:59:08 EST
I'd like a set of redirects or rewrite rules (i.e. apache-level settings, not
CGIs preferably) that I can put on the priority.redhat.com web servers to send
the users of the 6.2 up2date v1 client to a landing page on the RHN site so that
they can be upsold to instead of continuing to run 6.2 and using a service that
has no new updates.
Comment 1 Chip Turner 2003-04-14 11:37:37 EDT
you need the URLs to redirect -to- from RHN?  or the redirects themselves?
Comment 2 Need Real Name 2003-04-14 12:30:53 EDT
I'd like to send http[s]://priority.redhat.com/up2date/* ->
http[s]://rhn.redhat.com/foo/

The question is, what is "foo" on the rhn side for the up2date v1 users to land on?

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