Send credentials to same-origin

[topaxi]

Authorized API requests started failing using this addon. Allowing fetch to send credentials to same-origin solved this issue. I think it might sense to make this configurable, but I'm not sure how to do this.

By authorized in mean an Authorization HTTP header, but this should also address cases with cookies.

[JackCA]

I had this same issue and just reimplemented this PR against master at https://github.com/JackCA/ember-service-worker-cache-fallback/tree/add-credentials.

Is there any concern around this, @bcardarella?

[eshtadc]

I know this is a bit old now, but I agree that it should be a configuration. Taking a look.

[eshtadc]

Seems like there should be a more holistic approach here as any plugins dealing with caching do some sort of fetch call. I see in ember-service-worker-index that credentials are set to "include" but the rest do not supply credentials. I'm inclined to want to allow fetch init options (or at least a subset of them) to be set in the main ember-service-worker addon and read by any sw plugin that wants to use them.

[topaxi]

I guess since there is an alternative fix proposed, this issue can be closed :)