Public facing web application, Domino 8.5.1 on linux, accessed by all web browsers.
I have a “news” view in an application accessed via web browsers. Content for this view is created via a form that contains various fields that dictate how the data is displayed. E.g. an attachment might be in a “Content” document, a field setting in the document will dictate what happens when the user clicks the href link in the view: the document is opened in the same browser window, the attachment is opened in the same browser window or the attachment is launched in a new window, e.g:
My issue is:
When the document is configured to launch the attachment in a new window, intermittently, I will get a “page not found” in the new window. If you close the new window, click the link again, it will launch (or maybe the 3rd time). The code appears to be correct, and this issue can be “intermittently” reproduced across all browsers. I initially thought it was the file names, some files were named:
some Letter25.09.09.pdf
which was getting converted to:
plinksp/MADN-7X3BJW/$File/some%20Letter25.09.09.pdf
…but, again, since the name was getting converted correctly, it was still launching intermettently when I chnaged the name to something simple, e.g. SomeLetter.pdf
The default and anonymous access to database is “no access”. The documents are made public via a $PublicAccess field, the user is not authenticated with server.
Because of the intermittent-ness, I think this is a server setting issue…?
Here is an example from the DomLog.nsf (I changed the path…):
Request: GET /mypath…my.nsf/plinksp/MADN-7X8DJ2/$File/Somefile.pdf HTTP/1.1
Status: 404 NOT FOUND (Server could not find the given resource)
All files are well under 1Mb.
I am using Domino Web Internet Site docs, with compression turned on:
Compression Settings
Compress output: Enable
Include MIME types: text/; application/
Exclude MIME types: application/x-gzip; application/x-zip
Compress to file threshold: 1 MB
Minimum compress content length: 300 bytes
I “think” I have a work around at the moment, I am launching in the same window, not a new window e.g.:
…I haven’t yet had a “page not found”, so, at this stage at least, it would seem to indicate it’s something to do with the launching of a new window…?
I don’t think I am running into any GET or POST limitations, these are all GETs.
I would be very interested to hear any from anyone with any ideas or comments.
Thanks in advance.
Nick