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

Wrong Content-Disposition header when download epub (rfc1806) #1481

Closed
alkahan opened this issue Oct 13, 2015 · 8 comments
Closed

Wrong Content-Disposition header when download epub (rfc1806) #1481

alkahan opened this issue Oct 13, 2015 · 8 comments

Comments

@alkahan
Copy link

alkahan commented Oct 13, 2015

When download an epub file, the content-disposition header value is wrong:

Result:
Content-Disposition: attached; filename="title.epub"

Should be:
Content-Disposition: attachment; filename="title.epub"

see: http://www.ietf.org/rfc/rfc1806.txt

Impact:
The filename is not set properly on some devices like my Sony Reader, and use default filename "filename.bin". The device cannot open the file with that name.

@j0k3r
Copy link
Member

j0k3r commented Oct 13, 2015

I guess you are talking about the v1 ?
Feel free to provide a PR about that, it's an easy bug to fix.

➡️

@j0k3r j0k3r added the Easy bug label Oct 13, 2015
@alkahan
Copy link
Author

alkahan commented Oct 13, 2015

Yes in v1 :1.9.1.

You are right, I will provide a PR today.

@j0k3r
Copy link
Member

j0k3r commented Oct 13, 2015

@alkahan awesome ! Don't forget to target the dev branch instead of the master.

@tcitworld
Copy link
Member

The PR can also be submitted to the PHPePub project.

@alkahan
Copy link
Author

alkahan commented Oct 13, 2015

@tcitworld I have made a PR for PHPePub 3.30 branch. Current master and 4.0.0 rely on PHPZip and provide the right header value.

@tcitworld
Copy link
Member

Nice. wallabag v2 relies on PHPePub 4.0 so it will be fine.

@nicosomb
Copy link
Member

Can we close this issue?

@j0k3r
Copy link
Member

j0k3r commented Oct 19, 2015

We don't use sendBook in the v2, we built the response ourself.

@j0k3r j0k3r closed this as completed Oct 19, 2015
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

No branches or pull requests

4 participants