Full disclosure. We are using reverse proxy and I did see and article linked below regarding this. I published a document where the primary content filename had a semicolon in the filename. When I attempted to view the details page, my authentication prompt was triggered and I saw this where the thumbnails should be. It still was able to launch Creo View but even then, auth prompt was thrown again. Weird enough to post about. I can see in my system that I have only a dozen cases of this. Publishing actually creates more since the Creo view files use the filename as its identity.
Found these in the knowledge base:
https://www.ptc.com/en/support/article/CS249568?source=search
https://www.ptc.com/en/support/article/CS314720?source=search
I know its messing up the URL somehow. I will check Apache logs to see but easy enough to tell users to not do this. Still seems like a bug that should be handled. Actually, what concerns me more is the possibility for injection of attack via the filename. Any white hats out there?
We had a similar problem a couple of weeks ago.
Just that morning I had been reading the support articles that I get on a daily basis.
Among those articles, one mentioned a problem opening PDF files due to a specific version of Acrobat Reader DC.
After an endless row of tests, we discovered that the problem this person had was confined to some PDFs, created as a result of scanning, that would not open by clicking directly on the thumbnail.
The problem did not occur if Windchill was configured in Http but only in Https, so we thought it was due to some strange font generated by the scanning being mistranslated by the reverse proxy
We solved the problem by opening the PDF file directly from the representations tab as per the attached image.
