Difference when viewing PDF render with /workspace-server/ and /DocumentManager/

Question

Hi all,
There are 2 scenarios when viewing file in attachment:
1) When user is processing the form, they view the attachment in attachment tab. The url's format is: https://mydomain/workspace-server/documents/-6195445997301787088-16.pdf
2) My client's requirement is to view files in attachment tab even after the process is complete.
What i have done is to write a custom java component, retrieve attachment of the last task and return to user.
The url has format: https://mydomain/DocumentManager/docm1266831910962/53650adc3948bd502cf8c81d4885feec?type=Y XBwbGljYXRpb24vb2N0ZXQtc3RyZWFt
(I also found that the file is generated under GDS folder)
In both of the cases, navigateToURL() function is used to view the pdf in new window.
My trouble starts from here. In several client's machine, case 2 always ask them to save the form instead of viewing in the browser, while case 1 always can be viewable.
Below is the image of case 2 when i click in the link:
The strange thing is in local environment, both cases are working ...
Is there any idea why it happen?
My client is using windows xp, IE 6 and adobe reader 9. Some of them are using windows vista, IE 7 and adobe reader 9.
In local environment, we have tested successfully with
1)
Window XP
IE6/IE7/FireFox/Google Chrome
Adobe reader 9
2)
Window vista
IE7
Adobe reader 9
Regards,
Anh

Answer 1

You are confusing me
But first, the setContentTypeFromBasename() is an ES2 addition to the Document class.  Didn't realize this was a pre-ES2 case. Sorry about that.
Next, you say you are removing the ?type=ASDFASDFASDF from the url on the client. This must be there so the DocumentManager servlet can set the proper content-type in the http response.  I looked at the code and if it isn't there, no content type is set so it will be browser and os dependent on what it will do,although i would expect most to prompt.
And however your custom component and the short lived process work, that document output variable needs to have the proper content-type set in it (the Document has a setContentType() method in 8.2 but you will have to do the mapping from file extension to mime-type yourself in 8.2).  If it does and you don't remove the type parm from the url, then things will work.  But if that type parm isn't there or the content-type isn't set in the document output var, the browser will not know which application/plugin to launch and will prompt.
Jon