Web Start returns a Bad MIME Type error. Whats wrong?
This is from the Lopica Unofficial JWS FAQ. This is a very common problem and most likely caused by Web Start’s failed attempt to automatically detect your proxy settings. The “Bad MIME Type” error displayed by Web Start is somewhat confusing as it should really be a “Resource Not Found” error. Your proxy will send back an error page either in HTML or plain text instead of the requested JNLP descriptor if it fails to get the JNLP descriptor requested by Web Start. You can change your proxy settings for Web Start manually by starting the Application Manager and using the Preference panel. (Select File|Preferences to get there.
This is from the Lopica Unofficial JWS FAQ. This is a very common problem and most likely caused by Web Start’s failed attempt to automatically detect your proxy settings. The “Bad MIME Type” error displayed by Web Start is somewhat confusing as it should really be a “Resource Not Found” error. Your proxy will send back an error page either in HTML or plain text instead of the requested JNLP descriptor if it fails to get the JNLP descriptor requested by Web Start. You can change your proxy settings for Web Start manually by starting the Application Manager and using the Preference panel.
Related Questions
- Why do I get the error Bad CPU type in executable on installing Asymptote from the MAC OS binary?
- Why do I get the error Bad CPU type in executable on installing Asymptote from the MAC OS binary?
- What does bad disc, error, wrong discs or wrong region mean?
- I get a Bad MIME type error when accessing the JNLP file?
- I get a Bad MIME type error when accessing the JNLP file?
- Web Start returns a Bad MIME Type error. Whats wrong?
