The form in the database has a richtext field which may have attachment in it.Is there a way to prevent anonymous to download the attachment by the link …/$FILE/attachemtn.name?
What I can do is to hide the field, but I can’t acturally hide the attachment from the above link.
The anonymous users has the reader rights to the form.
Thanks.
Subject: Field control on the web
If the read-mode form for the document is set to “Treat contents as HTML” and the rich text fiels is left off of the form, you can use computed text (or a computed-for-display field) for the attachment links. Unlike with Notes-format forms, the attachments will not appear V2-style at the bottom of the form.
Subject: RE: Field control on the web
Yes,I’m doing exactly the same.But the attachment can still be downloaded thru the link like: http://…/view/docid/$FILE/attachment.name
I can only hide the attachment icon and the link but can’t prevent people who know the link from downloading the attachment.
any other ideas?
Subject: RE: Field control on the web
Users would need to know the name of the file in order to download it via a URL. If you want to change their access to the attachment altogether, either (1) change the ACL and/or readers fields so anonymous users cannot read the document or (2) pull the attachment out via script when the doc is saved and place it somewhere else where anonymous users won’t have access to it.
Subject: RE: Field control on the web
Thank you Stan and Erik.Maybe (2) is the work arround.
I really want to see if there is a Notes field level control on that.
The reason I ask for that is my website is free for people to upload the attachments, but I only want the login users to download the attachment through my own website. I notice half of the traffic are from download.com and znet for example. They just used my link for download without opening my web page.
Subject: RE: Field control on the web
Another possibility might be to collect the attachment on a completely different document in the first place. A response document may be a great way to handle this. You would need to create your own mechanisms for adding/deleting the attachments, but that should be fairly straightforward. This is a great way to handle multiple attachments, because Domino’s native capabilities for handling multiple attachments in one doc are a bit limited.
Subject: Thank you, Erik!! (eom)
Subject: RE: Field control on the web
Thay need to know the name of the file in order to get it. Why would they be aware of the filename if it’s not displayed anywhere? (You can use validation to keep people from adding the filename in plain text to any of the fields, if that’s an issue.)