> Hi everyone
>
> I'm having some rather confusing problems using PDB URLs. Let me
> elaborate.
Is this at the client or the server? (I ask because I think you have
mentioned some server-side files. Pleaes forgive me if I have got this
wrong!)
> > molviewer <pdb file> >
> So my .mime.types file has an entry that looks like
mime.types (no dot) is a server-side file (in httpd/conf or
somewhere similar) that determines the MIME type that the server prepends
to the file.
> > application/pdb pdb PDB
I think almost everyone has now changed to
chemical/pdb
Although it is not yet an IETF standard , it is working well at a de
facto level (:-) and Herny and I and reasonly confident that it will live
long and prosper.
> > and the corresponding .mailcap entry is
this is a client-side file and determines what action is taken when you
*receive* a file of a given MIME type.
>
> application/pdb; /usr/sg15/people/mjh/bin/molviewer.tcl %s
this will only work if the server sends you a file with the type
application/pdb
Since most servers have changed to chemical/pdb this may be your problem.
>
> (the path is correct).
>
>
> When I run
>
> netscape <local pdb file>
>
> it brings up molviewer with the correct file, or
>
> netscape <local pdb directory>
>
> it brings up the directory; clicking on a pdb file starts molviewer properly.
When you run a YorkClient <---> YorkServer
you won't have a problem. When you run a
YorkClient <---> OtherServer
*you* will have a problem at your browser. If you are offering PDGB
files from your *server* (and I think you are) then:
OtherClient <---> YorkServer
will cause all *your users* to have problems!
I hope this is the problem. We discussed at some length on the
chemime maillist whether we should use chemical/x-pdb or x-chemical/pdb and
Nat Borenstein (netguru) more or less said - just go ahead and use
chemical/pdb. So whilst, technically, you are following the exact letter
of the IETF convention, the rest of the world has already 'guessed the
future'!
> One thing I have noticed is that the pdb URLs that work are, for example
>
> <A HREF="/usr/sg17/people/proctor/pdb/1abf.pdb">
>
> while
>
> <a href=1crn.pdb>pdb file</a>
>
> does _not_ seem to work.
>
The BNF for HTML requires quotes. I have been sloppy in the past
and omitted quotes. 'Almost all' browsers don't seem to mind but a few
do. So URLs without quotes are syntactically wrong and should be
corrected. There is a weblint tool somewhere that will vet your HTML - I
just don't have the URL at present.
P.
------------------------------------------------------------------------------
Peter Murray-Rust | "Nothing exists except atoms and empty
pmr1716@ggr.co.uk | space; all else is opinion" (Democritos).
Protein Structure Group, Glaxo Group Research, Greenford, MIDDX, UB6 0HE, UK
------------------------------------------------------------------------------