What's the scenario where I need to change the mime type after I
have searched for it already?
So the application can easily check what actual MIME type has been used,
and dynamically change it if incorrect.
The component has excess of these Triggerxxx methods.
Because it's evolved over 15
What's the scenario where I need to change the mime type after I
have searched for it already?
So the application can easily check what actual MIME type has been used,
and dynamically change it if incorrect.
That's an unneeded double-check. If you are providing the MimeTypesList,
you will
Thanks, I'm using v 7.51, but somehow overlooked new demo and thought
the mime-type related component (and your comments) are for optional usage,
that is it allows for providing additional types which are rare and application
specific. Javascript is not in this number, obviously, so I supposed it
I think loading hundreds of types from Registry when 'js' is
missing in the default list is overkill, because most of them
are not Internet-involved.
Everyone has different requirements, TMimeTypeList is designed to support
email as well where many different file types may get sent as
On 10-11-2012 14:42, Stan wrote:
I think loading hundreds of types from Registry when 'js' is missing
in the
default list is overkill, because most of them are not Internet-involved.
It don't takes that long, but even so It's also my opinion..., If it's
not needed, don't do it.
Because of
Hi, everybody,
I propose a little but important fix for web-server component implementation.
In the module OverbyteIcsHttpSrv.pas, in the function DocumentToContentType,
just before the default latest clause with
else
Result := 'application/binary';
there should be added the
In the module OverbyteIcsHttpSrv.pas, in the function
DocumentToContentType
This function is now obsolete, the latest versions of the web server use
the new TMimeTypesList component which takes mapping from the Windows
classes registry, from a file or allows you to add your own extra MIME
