424306 - Export phpMyAdmin doesn't work

Status: RESOLVED INVALID

(Core :: Networking: HTTP, defect)

Description

[Nicolas Loeuillet]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.12; .NET CLR 2.0.50727) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.12; .NET CLR 2.0.50727) Gecko/20080201 Firefox/2.0.0.12

My database export (gz format) with phpMyAdmin 2.6.4-pl4 doesn't work with Firefox 3b4 (with IE6 or FF2, it's ok).

If you export without gz (sql format), it's ok.

Reproducible: Always

Steps to Reproduce:
1. export database (gz format)
2. try to import this file

Comment 1

[John]

I can confirm this. Anyone want to take on this bug?

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008040305 Minefield/3.0pre

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Unclear why this should block.

(In reply to comment #0)
> Steps to Reproduce:
> 1. export database (gz format)
> 2. try to import this file

Import into where? What's the actual result? What was the expected result?

Comment 3

[John]

The GZ file being downloaded is completely corrupted when exported from PhpMyAdmin. It works fine in Firefox 2 and other browsers (expected result is for a download of the compressed gzip archive). What actually happens is that Firefox does not download a gzipped file, but rather an uncompressed file, therefore, it is not an archive and will not open or import back to phpmyadmin and run the queries.

Maybe it is an issue with phpmyadmin and mime types, but I don;t know why it only doesn't work on Firefox 3.

Comment 6

[Sergio]

I confirm this. When you try to download a database from phpmyadmin ( I tried with both versions 2.9.1.1 and 2.10.1 ) it results on a corrupted zip or gzip. I hope this will be fixed as soon as possible.
Regards

Comment 9

[Matthias Versen [:Matti]]

I think this is invalid:

from bug 462526 :
===================================================================
HTTP/1.x 200 OK
Date: Sat, 01 Nov 2008 18:11:13 GMT
Server: Apache/2.2.6 (Win32) DAV/2 mod_ssl/2.2.6 OpenSSL/0.9.8e
mod_autoindex_color PHP/5.2.4
X-Powered-By: PHP/5.2.4
Set-Cookie: pma_fontsize=82%25; expires=Mon, 01-Dec-2008 18:11:13 GMT;
path=/phpmyadmin/; httponly
Set-Cookie: pma_theme=original; expires=Mon, 01-Dec-2008 18:11:13 GMT;
path=/phpmyadmin/; httponly
Expires: Sat, 01 Nov 2008 18:11:13 GMT
Cache-Control: private, max-age=10800, pre-check=10800
Last-Modified: Thu, 20 Sep 2007 16:35:14 GMT
Content-Encoding: x-gzip
content-disposition: attachment; filename="p_info.sql.gz"
Pragma: no-cache
Content-Length: 479
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: application/x-gzip
=================================================================

The server sends a content encoding x-gzip and that means that it must encode the file with gzip (would be double gzip encoded).
Can please someone check if the server encode this gzip file correctly with gzip or if it sends the gzip without encoding it again ?

==============================================================================
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html :
The Content-Encoding entity-header field is used as a modifier to the
media-type. When present, its value indicates what additional content codings
have been applied to the entity-body, and thus what decoding mechanisms must be
applied in order to obtain the media-type referenced by the Content-Type header
field.

Comment 10

[Kris Kelly]

Yes, it's to do with the content encoding, commenting out the line:

$content_encoding = 'x-gzip';

in export.php seems to resolve this for me.

Comment 11

[John]

This seems to work now. Can someone mark this worksforme?

Comment 12

[Matthias Versen [:Matti]]

I will mark it invalid because it's a myphpadmin bug.
Great that they fixed it now.