How to add a link to open a file without a Win10 security warning in iTextSharp v5

By -

When creating a new PDF file using iTextSharp I am able to create a link in the document using the .SetAnchor method that navigates to the specified URL when clicked, such as

anchor.SetAnchor(...some URL...);

However, all I really want the click to do is open or execute a specified file on my local Win10 machine, and this also works if I merely specify the file instead of a URL, such as

anchor.SetAnchor("notepad.exe");

The issue is that I must use iTextSharp to create many of versions of the PDF file, with each version having a different file name itself as well as a different name for the file the link opens. Although I have no problem getting this to work, the annoyance is that whenever I click the link in a new version I get a "Security Warning" popup from Windows wanting to know if the "connection" should be allowed.

Because the warning mentions a "connection" I get the feeling there may be a method something like SetAnchor that will produce a link specifically intended for opening files rather than URLs and that will not result in a Security Warning each time the name of the file the link represents is changed. If so, what is it? If not, is there some other reasonable approach to avoid the security warning? This is all being used on my local machine so I know there are no security issues with the PDFs or the files being opened.



from Recent Questions - Stack Overflow https://ift.tt/3kycn4r
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more