If the 'Content-Disposition' header is not set, the title/filename could still be derived from the last part of the URL, though preferably not from the URL entered by the user, but from the URL from which the PDF file has acutally been loaded, so as to correctly handle redirections. This way, the server can define which filename to use. Therefore I'd like to suggest deriving the tab title (and default filename for saving) from the filename indicated by the server's 'Content-Disposition' response header. Furthermore, even without any redirection, an URL may refer to a PDF document by other means than by its filename, for example by an ID, so that an URL such as "" may return a PDF document the original filename of which is "document.pdf", but the tab title becomes "some_id" instead. Boxes can be used to display things like location info, store hours, pictures, ads, etc. This PDF document is then loaded by PDF-XChange Editor into a new tab the title of which, however, is not "document" or "document.pdf" as one would expect, but "searchstring". You can add and remove as many boxes as you want. Let's say the database can be queried by requesting an URL such as "" the server then responds to such a request by http redirection to the search result located at "". However, the last part of the URL does not necessarily correspond to the actual title/filename of the loaded document. This title then is also used as the default filename when saving the loaded document as a local file. I use this feature a lot to load PDFs that are stored in a private database and accessible through a server via http.Īpparently PDF-XChange Editor uses the last part of the URL entered by the user as the title for the tab that opens after loading. It's great that PDF-XChange Editor is able to directly open URLs.
0 Comments
Leave a Reply. |