Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another attempt to solve content-encoding header issues #106

Merged
merged 1 commit into from
May 7, 2015

Conversation

fcheung
Copy link
Contributor

@fcheung fcheung commented May 7, 2015

see #75

identity should not be used as a content encoding
geemus added a commit that referenced this pull request May 7, 2015
Another attempt to solve content-encoding header issues
@geemus geemus merged commit 818c8e1 into fog:master May 7, 2015
@geemus
Copy link
Member

geemus commented May 7, 2015

Thanks!

@Maxim-Filimonov
Copy link

I don't think it's fixed.
We are experiencing empty content-type with v0.4.0 when using with middleman-s3_sync needed to downgrade all the way to 0.1.2 to fix it. See #130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants