Unable to view PDFs in TeamSite 6.5 SP3

I just upgraded to TeamSite 6.5 SP3 on our dev box. I've noticed in the UI I am unable to view PDFs, I get this message:

type application/pdf cannot be displayed in the browser window. You can download the file to your local system, or you can perform any of the standard VisualPreview actions using the toolbar

I've already checked the iw.cfg, I already have this in there:

[iwproxy_smartcontextedit_allowed]
_regex=[^?]+\.pdf(\?.*)?$=no
_default=yes

Any help would be greatly appreciated, thanks so much!

Find more posts tagged with

Comments

Phanie

I have never used this but was just referring manuals and it says "_default" should be the first line under iwproxy_smartcontextedit_allowed followed by regex, I would say give this an attempt

---
Phanie

mummey_nc

Thanks Phanie!

I moved the default entry to the top so it is the first line under [iwproxy_smartcontextedit_allowed], I then reset the server and tried again - still no luck Smiley Sad

I'm getting the same error.

I am able to successfully view a web page (.asp) within the TeamSite UI, then, within the web page I can click on a pdf link and the pdf link comes up fine in this scenario. So strange!

nipper

A few point, this error is typically a browser mime type setting error rather than TS (though there are likely cases where TS could cause it).

Can you verify that your browser will load PDFs correctly ?

As to the proxy settings, _default needs to be last, the rules are read and applied in order, so default=yes overrides everything else.

Finally, the manual suggests this for SCE

_regex=\.pdf(\?.*)?$=no

though yours *should* work as well

Andy

ISCBorisB

Thanks Phanie!

I moved the default entry to the top so it is the first line under [iwproxy_smartcontextedit_allowed], I then reset the server and tried again - still no luck I'm getting the same error.

I am able to successfully view a web page (.asp) within the TeamSite UI, then, within the web page I can click on a pdf link and the pdf link comes up fine in this scenario. So strange!

You must stop and re-start proxy Server after doing this. If I were you I would also change regex to something like
_regex=\.[Pp][Dd][Ff]$=no (_default is to be the first line, absolutely)

nipper

(_default is to be the first line, absolutely)

My bad, I thought it needed to be last like other parts of TS.

mummey_nc

Thank you so much!!!!!

Using this code in iw.cfg, I am now able to view the pdfs:

[iwproxy_smartcontextedit_allowed]
_default=yes
_regex=\.pdf(\?.*)?$=no

I also tried the code in the opposite order with default last (stopped/started iwproxy) and I am still able to view the pdfs.

Thank you so much for your help!!!!!!!!!!!!

nipper

Thank you so much!!!!!

Using this code in iw.cfg, I am now able to view the pdfs:

[iwproxy_smartcontextedit_allowed]
_default=yes
_regex=\.pdf(\?.*)?$=no

I also tried the code in the opposite order with default last (stopped/started iwproxy) and I am still able to view the pdfs.

Thank you so much for your help!!!!!!!!!!!!

You should follow Bo's suggestion about [Pp][Dd][Ff] in the regex. Windows is not case sensitive, but TeamSite is and if you have a foo.PDF it may fail.

ISCBorisB

My bad, I thought it needed to be last like other parts of TS.

Proxy rules processing *seem* indeed be reversed comparing to other TS services. Evaluation terminates on the first match, that's why
*specific* (detailed?) regexes should go before *generic* ones. I can only speculate that it has been done to improve performance.

If that's the case, _default is either an "exception to the exception" or perhaps is not considered a "proxy rule" in the first place

Adam Stoller

Thank you so much!!!!!

Using this code in iw.cfg, I am now able to view the pdfs:

[iwproxy_smartcontextedit_allowed]
_default=yes
_regex=\.pdf(\?.*)?$=no

I also tried the code in the opposite order with default last (stopped/started iwproxy) and I am still able to view the pdfs.

Thank you so much for your help!!!!!!!!!!!!

I generally find it easier to set the default to no and only enable the SCE for things like htm files - since the SCE injects javascript into the stream to do its thing - there are generally fewer file types for which it is applicable...just a thought anyway.