Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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

  • 6 답장
  • 4 이 문제를 만남
  • 5 보기
  • 최종 답변자: 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.