Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Mozilla 도움말 검색

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

자세히 살펴보기

Extensions are changed on download

  • 8 답장
  • 0 이 문제를 만남
  • 489 보기
  • 최종 답변자: feklee

more options

I realize that if a file is served with mime type Content-Type: application/pgp-encrypted, then its extension is changed by Firefox on Android to ".pgp". Apparently, Firefox for Android likes to modify extensions based on mime type.

Can this behavior be disabled?

I realize that if a file is served with mime type ''Content-Type: application/pgp-encrypted'', then its extension is changed by Firefox on Android to ".pgp". Apparently, Firefox for Android likes to modify extensions based on mime type. ''Can this behavior be disabled?''

모든 댓글 (8)

more options

Unfortunately, no. Firefox for desktop does the same.

more options

Thanks! I was hoping that there is an option in about:config.

The problem at hand is that .pgp somehow are not opened by OpenKeychain upon download, whereas .gpg files are.

Otherwise, Firefox on Android is attractive, especially the built-in PDF viewer. I hope this issue will be fixed.

more options

What is the rationale? Make sure that file extensions match mime type? (security)

In the meantime, I am trying to figure out if it is possible to have OpenKeychain show up as handler for .pgp files.

more options

Thanks! I would just like to understand the rationale.

I don't even mind so much the change of the extension. What I do mind is that OpenKeychain is not listed as an option to decrypt .pgp files. With ".gpg" files, that issue does not exist.

more options

Submit this at bugzilla.mozilla.org

more options

Thanks! But, as far as I understand it, it's not a bug. It seems to be intentional.

more options

Sorry if that didn't fix your issue. Do you want me to try asking someone that works on Firefox about this?

more options

Thanks, Khalid, but this seems by design. Of course, if a Firefox dev could clarify, this would be great.

The issue only happens with Content-Type: application/pgp-encrypted

I see it with filebrowser installed on my server. Interestingly their official demo server at demo.filebrowser.org does not show that issue (login: demo/demo). It serves files with Content-Type: application/octet-stream