-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Downloading a database with GZIP compression from PhpMyAdmin returns uncompressed files #17413
Comments
Hi @williamdes, |
I had my problems on "mysql.aruba.it".
With the test server "https://demo.phpmyadmin.net/STABLE" I have same problem but it only exports the first 74,824 Bytes. |
I can confirm what @Zio3D says. It exports only ~73 Kb (SQL only) and nothing else. Changing Isn't possible to check if As a matter of fact, even zip doesn't work for me. It exports only 136 bytes (zipped). Server configuration
Client configuration
|
Thanks for your comments, so this is a duplicate of #16042, right ? |
Yes. |
Duplicate of #16042 |
@williamdes , can you reopen this issue? |
Could you try #16042 (comment) just in case ? |
I'm sorry but I can't do this because the pages are managed by aruba.it. |
I've looked in to this quite a bit and have found nothing that clarifies the problem, only makes it more confusing. I'm doing tests with a relatively current master branch and trying a full database export rather than going to a specific table. With Firefox (97 on a Mac), I confirm that the gzip download is not compressed. The .zip file is a correctly-formed ZIP file, but when uncompressed, the SQL file is empty. Using Chrome (98 on a Mac), the gzip download is correct, and contains what appears to be a correct representation of the SQL file. The .zip is again correctly-formed, and the uncompressed SQL file is empty. Using Windows Edge (98 on Windows 11), the gzip and uncompressed SQL appear to be correct. Changing the mime_type in Export.php causes Firefox to download a correctly formed gzip file that contains the correct SQL file, and it appears to have no negative effect on the Chrome functionality. Based on these tests, it seems to me that we should make the change from This would require some additional research but https://bugzilla.mozilla.org/show_bug.cgi?id=1755324#c2 seems to me to suggest that there's some ambiguous specification that is causing issues; it isn't immediately clear to me if that's in the phpMyAdmin code or the webserver configuration. It seems Firefox may have changed something relatively recently that shifted this behavior, too. |
This can also be reproduced using docker. This gives you control over phpmyadmin version and allow to edit its files. In empty directory create version: '3.7'
services:
phpmyadmin:
image: phpmyadmin:latest
ports:
- "8000:80"
environment:
MYSQL_USERNAME: root
MYSQL_ROOT_PASSWORD: root
db:
image: mysql:5.7
command: ["--default-authentication-plugin=mysql_native_password"]
ports:
- 3306:3306
environment:
MYSQL_ROOT_PASSWORD: root
MYSQL_DATABASE: database
MYSQL_USER: user
MYSQL_PASSWORD: password run go to |
I think this was recently resolved, let me know - image: phpmyadmin/phpmyadmin:latest
+ image: phpmyadmin:latest |
I thought I am using an original image 😱 Thanks for the heads-up, I have switched to I still get uncompressed file when downloading gzip export from phpmyadmin 5.2.0 on Firefox 101.0 (no issues in Chrome) |
Describe the bug
Since version 94.0.2 of Mozilla Firefox (64 bit) for Windows 10 64 bit, exporting a database with GZIP compression from PhpMyAdmin results in an uncompressed text file.
I report this bug to PhpMyAdmin because the ticket "https://bugzilla.mozilla.org/show_bug.cgi?id=1755324" on Firefox guides me to think about a PhpMyAdmin bug.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The saved file must be a GZIP compressed .SQL file.
Server configuration
Client configuration
Additional context
As I indicated in "### Describe the bug", I report this bug to PhpMyAdmin because the ticket "https://bugzilla.mozilla.org/show_bug.cgi?id=1755324" on Firefox guides me to think about a PhpMyAdmin bug.
It is strange that with the previous versions of Mozilla Firefox 94.0.2 the export worked correctly.
Thanks.
The text was updated successfully, but these errors were encountered: