Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #997
Closed
Open
Issue created Nov 01, 2016 by Administrator@rootContributor

Document deployment to S3

Created by: wolovim

Description

When deploying CRA apps to S3, the error document is effectively ignored by IE11. This causes all routes outside of the root route to reach IE's default 404 page. I have not yet tested this on other IE versions.

Expected behavior

If error document is set to index.html, the application should still display the App.js component when visiting <S3-route>/anything. (Alternatively, if a customerror.html is set, it should display that, but doesn't.)

Chrome, Firefox and Safari perform this behavior as expected.

Actual behavior

IE default 404 page.

Environment

  1. npm ls react-scripts: react-scripts@0.7.0
  2. node -v: v5.5.0
  3. npm -v: 3.5.3

Have tested from:

  1. Operating system: Win 8.1
  2. Browser and version: IE11

Reproducible Demo

I've got an example S3 deployment set up. You'll notice that the root route works fine, but you'll get the IE 404 page with any addition to the URL.

S3 Configuration:

The bucket has an open permissions policy:

{
	"Version": "2016-11-1",
	"Statement": [
		{
			"Sid": "AddPerm",
			"Effect": "Allow",
			"Principal": "*",
			"Action": [
				"s3:GetObject"
			],
			"Resource": [
				"arn:aws:s3:::demo-party/*"
			]
		}
	]
}

and is configured for static website hosting: screen shot 2016-11-01 at 10 39 56 am

More than happy to help debug further, but I'm about out of ideas on my end.

Assignee
Assign to
Time tracking