How to check all content-type values?

I have some tasks where I have to open xml document in related application, so I had to know the content type values. I did not know that it could be checked in regedit :-)

so here is a way how we can look at it

HKEY_CLASSES_ROOT \ Mime \ Database \ Content Type \

f.x. for excel it will be like this

Print {Content-Type:application/vnd.ms-excel}
Print {Cache-Control: public, must-revalidate}
Print {Expires: Sat, 26 Jul 1997 05:00:00 GMT}
Print xml_output

got Lotus Notes 8.5.1 FP1 installed ! who will be last ? :)

There are many fixes in that fix pack, so will see how it works :-)

Open XFDF file in Browser using Abobe Reader

I was facing with one simple problem. I had XFDF file on our web suite. Users open that XFDF file as URL (http://database/view/doc/$File/fileName) but it did not open in Adobe Reader, but in Browser as XML. I looked around and found solution. Add these line before XFDF output and it will start to work.

Print {Content-Type:application/vnd.adobe.xfdf}
Print {Cache-Control: public, must-revalidate}
Print {Expires: Sat, 26 Jul 1997 05:00:00 GMT}
Print xml_output

How to open XFDF file from IE in Adobe Reader?

I have really interesting problem. I have posted XFDF file on my site and planning that user will click on it and get PDF file opened. But the strange this is that each browser has different behavior:

on my PC I have set associated application for xfdf file - Adobe Reader.
1) IE opens my xfdf file in XML format, and that's all. that's the biggest pain,
2) FF opens it in good way, but anywhere it ask which application to use when open xfdf file.
3) Chrome, just download files without anything.

Any ideas? :) I will update my post later if I solve the problem

iText announced new version of their product 5

I use iText library in some of my LN applications, so I check their site sometimes for updates. Today I found that they announced new version - iText 5 (last one was 2.1.7).
I tried to update my code with that library, but I had to do some changes before, because new library has some changes in naming.

Anywhere it is really good that iText did not stop and moving forward, that's cool. Good job