[FOLIO-1174] Redirected URLs in 'dev.folio.org' go to the origin S3 bucket rather than the CloudFront URL Created: 04/Apr/18  Updated: 11/Jan/19  Resolved: 11/Jan/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: David Crossley Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: doc
Remaining Estimate: Not Specified
Time Spent: 1 hour
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-1179 Tidy all documentation in repositorie... Closed
relates to FOLIO-646 Implement improved navigation dev.f.o... Closed
relates to FOLIO-966 Enable URL redirection for dev.f.o Closed
Sprint:

 Description   

With the recent commits to FOLIO-646 Closed , `dev.folio.org/community/cla-process/` is redirecting to `devdocwebsite-websitemasterbucket-19z4dx2nejmtu.s3-website-us-east-1.amazonaws.com/guidelines/cla-process/` rather than `dev.folio.org/guidelines/cla-process`. The `s3-website-config.json` file has this stanza:

    {
      "Condition": {
        "KeyPrefixEquals": "community/cla-process"
      },
      "Redirect": {
        "ReplaceKeyWith": "guidelines/cla-process"
      }
    },


 Comments   
Comment by Peter Murray [ 04/Apr/18 ]

According to AWS, this is working as designed (emphasis added):

If you change the location of an object on the origin server, you can configure your web server to redirect requests to the new location. After you configure the redirect, the first time a viewer submits a request for the object, CloudFront Front sends the request to the origin, and the origin responds with a redirect (for example, 302 Moved Temporarily). CloudFront caches the redirect and returns it to the viewer. CloudFront does not follow the redirect.

Comment by David Crossley [ 11/Jan/19 ]

Closed as Done, as there is no Jira resolution for "Disappointed".

Generated at Thu Feb 08 23:11:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.