You are trying to solve an impossible problem. As you observed, all desktop browsers report back that they access all data types, and will gladly suck down any data that you pass to them. In cases of plug-in data, that data would start the plug in, while in others, the user might be asked where to save the data or other means. There is absolutely no way via standard means to determine whether a plug-in exists on the end computer.

The only browsers that I know of that will not accept */* mime types are some of the newer WAP browsers and a schmattering of text-to-voice ones, but nothing mainstream yet.

Now, if this plug-in that you are using has a way to delieve content that allows a user to click a link to go elsewhere (Flash, eg), then you can use that as a way to 'guard' the rest of your site; if the user has the plug-in, they'll see the short animation, and you can instruct them to "click here" to continue. Those that don't have it will have no idea where the enterance is and thus will not visit the site.

(My web ethics note: this is bad bad bad bad bad bad bad. 99% of the time, forcing the use of a plugin to delieve site contents is very very bad and not necessary. Plugin data should only be used to enhance the site's appearence and not hide content from users that can't use that plug-in. The 1% of the time where this is not the case are sites that are meant to demonstrate the abilities of these plugins. But this is my ethical opinion, and has no bearing on the tech answer above.)

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

In reply to Re: Server-side plug-in detection? by Masem
in thread Server-side plug-in detection? by Soliloquy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.