LiteSpeed Technologies
Download Download     Blog Blog     Wiki Wiki     Forum Forum     Store     Contact Contact    

Go Back   LiteSpeed Support Forums > LiteSpeed Web Server > Install/Configuration > Context -> MIME Type setting does not work as described in documentation

Reply
 
Thread Tools Display Modes
  #1  
Old 08-04-2006, 04:15 AM
andreas andreas is offline
Senior Member
 
Join Date: Aug 2006
Posts: 91
Default Context -> MIME Type setting does not work as described in documentation

1. When I enter the example from the documentation

image/jpg jpeg jpg, image/gif gif

in the "Mime Type" field of a static context, I get the strange error message

*invalid format - image/jpg, syntax is MIME_type suffix suffix, next MIME_type... MIME type is like text/html, followed by one or more suffix types separated by space. Use comma to separate different MIME types. invalid format - jpeg, syntax is MIME_type suffix suffix, next MIME_type... MIME type is like text/html, followed by one or more suffix types separated by space. Use comma to separate different MIME types. invalid format - jpg, syntax is MIME_type suffix suffix, next MIME_type... MIME type is like text/html, followed by one or more suffix types separated by space. Use comma to separate different MIME types. invalid format - image/gif, syntax is MIME_type suffix suffix, next MIME_type... MIME type is like text/html, followed by one or more suffix types separated by space. Use comma to separate different MIME types. invalid format - gif, syntax is MIME_type suffix suffix, next MIME_type... MIME type is like text/html, followed by one or more suffix types separated by space. Use comma to separate different MIME types.

2. When I enter the mime type "application/atom+xml" in the "Force MIME Type" field, I get this warning message after restart:
can't set 'Forced Type', undefined MIME Type application/atom+xml
Reply With Quote
  #2  
Old 08-04-2006, 07:08 AM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,603
The first one might be MIME type syntax validation problem in admin interface. Will check.

The second one is beause "application/atom+xml" must be defined as a MIME type first.
Reply With Quote
  #3  
Old 08-15-2006, 07:42 AM
andreas andreas is offline
Senior Member
 
Join Date: Aug 2006
Posts: 91
How do I define it as a mime type?

Btw, it works as expected when I use the field "default MIME type" instead of "force mime type".

Another problem: the "compressible types" field doesn't accept "application/atom+xml", probably because of the "+".
Reply With Quote
  #4  
Old 08-15-2006, 08:35 AM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,603
Just add it to "MIME Type" or change the global MIME definition file.

The "+" in MIME type problem will be fixed soon, it is the admin interface, you can add that in httpd_config.xml manually in the mean time.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Setting up External App Context artagesw Install/Configuration 16 06-12-2007 11:49 AM
Context-level problems setting custom HTTP headers Marcus Install/Configuration 3 04-03-2007 09:35 PM
authorization realm in rails context jdan Install/Configuration 2 10-19-2006 07:11 PM
Perl/FastCGI Probs - MIME type [€¤] for suffix '.fpl'... athanasius CGI/Perl/Python 3 02-08-2006 05:33 PM
Context with "exp: ..." URI don't seem to work Roman2K Bug Reports 7 11-01-2005 09:10 AM


All times are GMT -7. The time now is 08:44 AM.



- Archive - Top
© Copyright 2003-2011 LiteSpeed Technologies, Inc. All rights reserved. Privacy Policy.