phpmyadmin / phpmyadmin/phpmyadmin

Downloading a database with GZIP compression from PhpMyAdmin returns uncompressed files

Open
#17,413 15 comments 3 reactions 1 assignee View on GitHub

@williamdes is already working on this.

Since Feb 21, 2022.

affects/5.2 Bug duplicate waiting on upstream
Dominant language
PHP
Stars
7.9k
Forks
3.6k
Avg merge
4d 18h
Merged PRs (30d)
36

Description

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:

  1. With "Mozilla Firefox" (version greater than or equal to 94.0.2, for example 97.0.1) go to 'https://demo.phpmyadmin.net/STABLE/'.
  2. On "Username:" field, insert 'root'. Press 'Go'.
  3. Click on a database (for example 'egzamin ') and then in the top bar click 'Export'.
  4. On "Export method:" select "Custom - display all possible options".
  5. On "Compression:" select "gzipped".
  6. Click "Go" at the bottom right of the page.
  7. Save the file and then read with notepad (with notepad++ is more easy), it is result in .SQL format and not in compressed GZIP format.
Expected behavior

The saved file must be a GZIP compressed .SQL file.

Server configuration
Client configuration
  • Browser: Mozilla Firefox 97.0.1
  • Operating system: Windows 10 Pro 21H2 64 bit.
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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.