Tab title/filename when opening from URL
Posted: Mon Jul 15, 2019 10:07 am
It's great that PDF-XChange Editor is able to directly open URLs. I use this feature a lot to load PDFs that are stored in a private database and accessible through a server via http.
Apparently PDF-XChange Editor uses the last part of the URL entered by the user as the title for the tab that opens after loading. This title then is also used as the default filename when saving the loaded document as a local file. However, the last part of the URL does not necessarily correspond to the actual title/filename of the loaded document.
Let's say the database can be queried by requesting an URL such as "https://www.example.com/pdfdatabase/search/searchstring"; the server then responds to such a request by http redirection to the search result located at "https://www.example.com/pdfdatabase/document.pdf". 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". 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 "https://www.example.com/pdfdatabase/some_id" may return a PDF document the original filename of which is "document.pdf", but the tab title becomes "some_id" instead.
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. This way, the server can define which filename to use. 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.
What do you think`?
Apparently PDF-XChange Editor uses the last part of the URL entered by the user as the title for the tab that opens after loading. This title then is also used as the default filename when saving the loaded document as a local file. However, the last part of the URL does not necessarily correspond to the actual title/filename of the loaded document.
Let's say the database can be queried by requesting an URL such as "https://www.example.com/pdfdatabase/search/searchstring"; the server then responds to such a request by http redirection to the search result located at "https://www.example.com/pdfdatabase/document.pdf". 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". 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 "https://www.example.com/pdfdatabase/some_id" may return a PDF document the original filename of which is "document.pdf", but the tab title becomes "some_id" instead.
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. This way, the server can define which filename to use. 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.
What do you think`?
