1 person found this helpful
Regarding redirecting, it is possible, but it's up to the server-side script to return a response that causes this to happen. The most reliable way of doing this in my experience is to return an FDF that causes the redirect to occur.
The security issues are pretty much the same as with an HTML form. If you use SSL (HTTPS), it should be fine.
Regarding submitting as "HTML" form, yes, the format of the data is the same. PDF forms behave a bit differently than HTML forms, however. For example, you can have multiple fields with the same name but different values in an HTML form. As you know, if multiple fields have the same name in a PDF form, the values will be the same.
A PDF can be prevented from being printed using standard password security restrictions, but it must be downloaded in order to be used. When a use configure Reader/Acrobat to display a PDF in the browser, it is downloaded to a temporary location. Since the form will not be printed, it seems to me there is less reason to use a PDF form.
The biggest problem is not all users have Reader installed, or have it configured to open in their browser. A PDF form can still submit when it's being viewed outside of a browser though. The problem then becomes what sort of response should the server return with.
Thanks for the information.
Yes, I agree that there is less reason for it to be a PDF form (Actually, no real reason other than the original form already exists in PDF), but I am unfortunately in the position that my input in this project is not necessarily being considered (my company is following direct -and inconsistent- directions from the client, and I have no contact with the client to ask questions about what their actual needs are). I have been told to give the client the 'Tomato' that they are asking for, even though they are describing an 'Apple'.
The reason this form is not meant to be printed is that we have replaced the 'Signature' fields from the original form with checkboxes that the user must check to confirm they have 'signed' the document. If they are to print/fax/whatever the document, they should use the original form, not this one. And I am still trying to explain to them that this would be better served with an HTML web form, but I fear I am losing that battle.
I have brought up the fact that it is not 100% guaranteed that Acrobat will be available in the browser, although I can only guess that it is less than likely that anyone will not have some sort of PDF viewer available to their browser.
I will also mention that issues may arise if the file is not submitted from within the browser.