為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Fileupload issue. Unable to get the full local directory path of the file uploaded

  • 6 回覆
  • 4 有這個問題
  • 1 次檢視
  • 最近回覆由 cor-el

more options

Fileupload Applet Issue with Firefox 15:

When uploading a file using our application, file that is being uploaded is hashed using a signed Applet. This is working fine in IE and FF version lower than FF15.

Signed applet needs to hash file contents but it is is unable to read the full path of the uploaded file, and thus failing. Applet expects the full path of the file that has been uploaded

Is there any way to get the full file path?

Fileupload Applet Issue with Firefox 15: When uploading a file using our application, file that is being uploaded is hashed using a signed Applet. This is working fine in IE and FF version lower than FF15. Signed applet needs to hash file contents but it is is unable to read the full path of the uploaded file, and thus failing. Applet expects the full path of the file that has been uploaded Is there any way to get the full file path?

所有回覆 (6)

more options

This is a Java applet? And it's definitely a change in Firefox 15 (i.e., problem exists in Fx15 in the previous JREs, and does not exist in Fx14 in the current JRE)?

more options

Hi Jscher2000,

Yes, issue does not exist in FF14 and lower versions, e.g. Ff3.6.x even with current JRE 1.7.

Any solution you can suggest?

more options

I don't do any plugin-content development myself, so I'm not familiar with any special issues in communications between applets and Firefox.

Is the upload control part of the applet or an <input type="file"> in the page? There seem to be frequent changes with the latter.

more options

Sounds like a 'victim' of the XPCOM UniversalXPConnect changes caused by this bug.

more options

Hi cor-el,

Seems like it. I was googling to see and came across XPCOM also. Is this really a bug or a new feature?

more options

Is not a new feature and not really a bug, but rather a security change that they have cleaned up code and removed the ability to use UniversalXPConnect that made it possible in older Firefox versions to get enhanced privileges.
That is no longer possible, so any code that relies on it will fail silently.
You will now require an extension to run any code that requires enhanced XPCOM permissions.