I just heard back from Jason, I asked him what he thought the problem was, I guessed maybe an output compression issue and he agrees. This is what he told me:
Yea, that looks like the server is configured with some sort of PHP-based output compression, or is running on a server that’s unable to detect the MIME type served via PHP. This is the same issue that was affecting file downloads on some servers before we implemented the .htaccess exclusion recently. I should have included the exportation files in that .htaccess rule as well, just to avoid this issue.
Since I didn’t, we’ll have to deal with this on a case-by-case basis for now. In this case, I’d recommend that she make the following adjustment in s2Member.
[hilite mono]/s2member-pro/includes/classes/exports-in.inc.php[/hilite]
at line #239 find this:
header ("Content-Encoding:");
Change that to:
header ("Content-Encoding: none");
That’s actually invalid, but seems to work as a quick hack in many cases. The better solution is the .htaccess rewrite rule, but it’s not possible to do that with export files just yet. I’ll take care of that asap. If that doesn’t work, we’ll need to know more about the hosting environment (i.e. running Apache? if so, is GZIP enabled? if so, how exactly, mod_deflate?).
Could you provide that info? Also, try that hack and see if it fixes the issue.
I hope that helps.