You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Andrew Black (JIRA)" <ji...@apache.org> on 2006/10/16 22:24:34 UTC
[jira] Created: (INFRA-989) Bad Mime-Type/Content-Encoding for
files
Bad Mime-Type/Content-Encoding for files
----------------------------------------
Key: INFRA-989
URL: http://issues.apache.org/jira/browse/INFRA-989
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Andrew Black
Priority: Minor
Martin Sebor and I have been working to provide some files within his page on people.apache.org, and are having problems determining the extension to use for these files.
The files in question are text files which were gziped to save disk space. In an effort to save bandwidth, we are currently transfering the files to the apache servers in compressed form, and want them to be sent to the user with the Content-Type set to 'text/plain', and the Content-Encoding set to 'x-gzip'. I believe this combination of header types should allow the files to be viewed within the web browser, rather than forcing the use of an external program to decompress and/or view them.
We have tried giving the files a suffix of '.gz.txt' and '.txt.gz', but neither has provided us with the desired behavior. We have also tried adding a .htaccess file to the directory where the files reside, containing the following 3 lines, (and possibly without the second line) also without success.
AddType text/plain .txt
AddType application/x-gzip .gz
AddEncoding x-gzip .gz
I can see several possible ways to resolve this.
This first is to use the correct suffix for the files, if one is configured.
The second is to correct any errors in the .htaccess file that was tried.
The third (if .htaccess files are disabled on the server) is to alter the server configuration to handle the .gz.txt file extension or another suitable extension.
The final option is to transmit the files in their uncompressed form.
--Andrew Black
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-989) Bad Mime-Type/Content-Encoding for files
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-989?page=all ]
Henri Yandell closed INFRA-989.
-------------------------------
Resolution: Won't Fix
Closing the issue as suggested by the original poster.
> Bad Mime-Type/Content-Encoding for files
> ----------------------------------------
>
> Key: INFRA-989
> URL: http://issues.apache.org/jira/browse/INFRA-989
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Andrew Black
> Priority: Minor
>
> Martin Sebor and I have been working to provide some files within his page on people.apache.org, and are having problems determining the extension to use for these files.
> The files in question are text files which were gziped to save disk space. In an effort to save bandwidth, we are currently transfering the files to the apache servers in compressed form, and want them to be sent to the user with the Content-Type set to 'text/plain', and the Content-Encoding set to 'x-gzip'. I believe this combination of header types should allow the files to be viewed within the web browser, rather than forcing the use of an external program to decompress and/or view them.
> We have tried giving the files a suffix of '.gz.txt' and '.txt.gz', but neither has provided us with the desired behavior. We have also tried adding a .htaccess file to the directory where the files reside, containing the following 3 lines, (and possibly without the second line) also without success.
> AddType text/plain .txt
> AddType application/x-gzip .gz
> AddEncoding x-gzip .gz
> I can see several possible ways to resolve this.
> This first is to use the correct suffix for the files, if one is configured.
> The second is to correct any errors in the .htaccess file that was tried.
> The third (if .htaccess files are disabled on the server) is to alter the server configuration to handle the .gz.txt file extension or another suitable extension.
> The final option is to transmit the files in their uncompressed form.
> --Andrew Black
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-989) Bad Mime-Type/Content-Encoding for
files
Posted by "Andrew Black (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-989?page=comments#action_12442942 ]
Andrew Black commented on INFRA-989:
------------------------------------
As this likely isn't an apache issue, this ticket should probably be closed.
One other clue that may point to a browser bug is that Martin and I were both able to view the page inline when the Content-Type was sent as 'text/plain' (as was produced by one of our internal webservers) rather than 'text/plain; charset=ISO-8859-1'.
> Bad Mime-Type/Content-Encoding for files
> ----------------------------------------
>
> Key: INFRA-989
> URL: http://issues.apache.org/jira/browse/INFRA-989
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Andrew Black
> Priority: Minor
>
> Martin Sebor and I have been working to provide some files within his page on people.apache.org, and are having problems determining the extension to use for these files.
> The files in question are text files which were gziped to save disk space. In an effort to save bandwidth, we are currently transfering the files to the apache servers in compressed form, and want them to be sent to the user with the Content-Type set to 'text/plain', and the Content-Encoding set to 'x-gzip'. I believe this combination of header types should allow the files to be viewed within the web browser, rather than forcing the use of an external program to decompress and/or view them.
> We have tried giving the files a suffix of '.gz.txt' and '.txt.gz', but neither has provided us with the desired behavior. We have also tried adding a .htaccess file to the directory where the files reside, containing the following 3 lines, (and possibly without the second line) also without success.
> AddType text/plain .txt
> AddType application/x-gzip .gz
> AddEncoding x-gzip .gz
> I can see several possible ways to resolve this.
> This first is to use the correct suffix for the files, if one is configured.
> The second is to correct any errors in the .htaccess file that was tried.
> The third (if .htaccess files are disabled on the server) is to alter the server configuration to handle the .gz.txt file extension or another suitable extension.
> The final option is to transmit the files in their uncompressed form.
> --Andrew Black
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-989) Bad Mime-Type/Content-Encoding for
files
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-989?page=comments#action_12450920 ]
Martin Sebor commented on INFRA-989:
------------------------------------
It turned out to be a browser issue. After removing Mozilla's default helper application associated with files with the .gz suffix (gunzip) the browser is able to open the files.
> Bad Mime-Type/Content-Encoding for files
> ----------------------------------------
>
> Key: INFRA-989
> URL: http://issues.apache.org/jira/browse/INFRA-989
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Andrew Black
> Priority: Minor
>
> Martin Sebor and I have been working to provide some files within his page on people.apache.org, and are having problems determining the extension to use for these files.
> The files in question are text files which were gziped to save disk space. In an effort to save bandwidth, we are currently transfering the files to the apache servers in compressed form, and want them to be sent to the user with the Content-Type set to 'text/plain', and the Content-Encoding set to 'x-gzip'. I believe this combination of header types should allow the files to be viewed within the web browser, rather than forcing the use of an external program to decompress and/or view them.
> We have tried giving the files a suffix of '.gz.txt' and '.txt.gz', but neither has provided us with the desired behavior. We have also tried adding a .htaccess file to the directory where the files reside, containing the following 3 lines, (and possibly without the second line) also without success.
> AddType text/plain .txt
> AddType application/x-gzip .gz
> AddEncoding x-gzip .gz
> I can see several possible ways to resolve this.
> This first is to use the correct suffix for the files, if one is configured.
> The second is to correct any errors in the .htaccess file that was tried.
> The third (if .htaccess files are disabled on the server) is to alter the server configuration to handle the .gz.txt file extension or another suitable extension.
> The final option is to transmit the files in their uncompressed form.
> --Andrew Black
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-989) Bad Mime-Type/Content-Encoding for
files
Posted by "Joshua Slive (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-989?page=comments#action_12442724 ]
Joshua Slive commented on INFRA-989:
------------------------------------
The server is sending
HTTP/1.1 200 OK
Date: Mon, 16 Oct 2006 22:08:30 GMT
Server: Apache/2.2.3 (Unix) SVN/1.3.1-dev mod_ssl/2.2.3 OpenSSL/0.9.8b DAV/2
Last-Modified: Wed, 11 Oct 2006 23:14:52 GMT
ETag: "2dc0db1-a4dab-38e39300"
Accept-Ranges: bytes
Content-Length: 675243
Content-Type: text/plain; charset=ISO-8859-1
Content-Encoding: x-gzip
So I don't see a server-config issue.
> Bad Mime-Type/Content-Encoding for files
> ----------------------------------------
>
> Key: INFRA-989
> URL: http://issues.apache.org/jira/browse/INFRA-989
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Andrew Black
> Priority: Minor
>
> Martin Sebor and I have been working to provide some files within his page on people.apache.org, and are having problems determining the extension to use for these files.
> The files in question are text files which were gziped to save disk space. In an effort to save bandwidth, we are currently transfering the files to the apache servers in compressed form, and want them to be sent to the user with the Content-Type set to 'text/plain', and the Content-Encoding set to 'x-gzip'. I believe this combination of header types should allow the files to be viewed within the web browser, rather than forcing the use of an external program to decompress and/or view them.
> We have tried giving the files a suffix of '.gz.txt' and '.txt.gz', but neither has provided us with the desired behavior. We have also tried adding a .htaccess file to the directory where the files reside, containing the following 3 lines, (and possibly without the second line) also without success.
> AddType text/plain .txt
> AddType application/x-gzip .gz
> AddEncoding x-gzip .gz
> I can see several possible ways to resolve this.
> This first is to use the correct suffix for the files, if one is configured.
> The second is to correct any errors in the .htaccess file that was tried.
> The third (if .htaccess files are disabled on the server) is to alter the server configuration to handle the .gz.txt file extension or another suitable extension.
> The final option is to transmit the files in their uncompressed form.
> --Andrew Black
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-989) Bad Mime-Type/Content-Encoding for
files
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-989?page=comments#action_12442702 ]
Martin Sebor commented on INFRA-989:
------------------------------------
Here's an example of a gzipped text file that we'd like to be able to open in the browser simply by pasting the link into it:
http://people.apache.org/~sebor/stdcxx/results/aix-52-visualage-32b-6.0.0-11d-log.gz.txt
It actually seems to work fine in Mozilla on my Windows XP laptop but it doesn't work with the same browser running on Linux (at least not on my workstation). If it's a matter of setting up the browser how do I make it work?
> Bad Mime-Type/Content-Encoding for files
> ----------------------------------------
>
> Key: INFRA-989
> URL: http://issues.apache.org/jira/browse/INFRA-989
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Andrew Black
> Priority: Minor
>
> Martin Sebor and I have been working to provide some files within his page on people.apache.org, and are having problems determining the extension to use for these files.
> The files in question are text files which were gziped to save disk space. In an effort to save bandwidth, we are currently transfering the files to the apache servers in compressed form, and want them to be sent to the user with the Content-Type set to 'text/plain', and the Content-Encoding set to 'x-gzip'. I believe this combination of header types should allow the files to be viewed within the web browser, rather than forcing the use of an external program to decompress and/or view them.
> We have tried giving the files a suffix of '.gz.txt' and '.txt.gz', but neither has provided us with the desired behavior. We have also tried adding a .htaccess file to the directory where the files reside, containing the following 3 lines, (and possibly without the second line) also without success.
> AddType text/plain .txt
> AddType application/x-gzip .gz
> AddEncoding x-gzip .gz
> I can see several possible ways to resolve this.
> This first is to use the correct suffix for the files, if one is configured.
> The second is to correct any errors in the .htaccess file that was tried.
> The third (if .htaccess files are disabled on the server) is to alter the server configuration to handle the .gz.txt file extension or another suitable extension.
> The final option is to transmit the files in their uncompressed form.
> --Andrew Black
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira