gatsby-uc/gatsby-plugin-s3

Add support for force and statusCode on redirects

Open

#67 opened on May 25, 2019

View on GitHub
 (0 comments) (1 reaction) (0 assignees)TypeScript (104 forks)github user discovery
enhancementgood first issuepriority: low

Repository metrics

Stars
 (206 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

According to the documentation for createRedirect, some plugins support the non-standard redirect parameters force and statusCode. It might be nice for us to support these too.

With Redirection Rules, we can support force by adding/removing the HttpErrorCodeReturnedEquals: '404' condition. We can support statusCode by overriding the HttpRedirectCode redirect value.

With redirect objects (#64) we can support force by choosing whether to upload the content object or the redirect object in the event of a conflict. This would require a bit of a change to the upload logic. It's not possible to use redirect objects for anything other than 301, so they would have to still be handled by Redirection Rules.

Contributor guide

Research direction
Investigate how the plugin currently handles redirects and how to modify Redirection Rules and redirect objects to support force and statusCode.
Tech stack
typescriptreactnodejsaws
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GatsbyAWS S3Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70