This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Denne tråden ble arkivert. Still et nytt spørsmål dersom du trenger hjelp.

Why firefox is not sending 'filename' parameter for form file parts encoded as specified in rfc2388?

  • 3 svar
  • 1 har dette problemet
  • 5 views
  • Siste svar av cor-el

hablutzel1
hablutzel1
more options

rfc2388 states:

The original local file name may be supplied as well, either as a "filename" parameter either of the "content-disposition: form-data" header or, in the case of multiple files, in a "content-disposition: file" header of the subpart. The sending application MAY supply a file name; if the file name of the sender's operating system is not in US-ASCII, the file name might be approximated, or encoded using the method of RFC 2231.

But firefox is just sending 'filename' parameter encoded with the page encoding or the form accept-charset, this is, it is sending raw UTF-8 or the choosen encoding.

Which is the reason for this?

rfc2388 states: The original local file name may be supplied as well, either as a "filename" parameter either of the "content-disposition: form-data" header or, in the case of multiple files, in a "content-disposition: file" header of the subpart. The sending application MAY supply a file name; if the file name of the sender's operating system is not in US-ASCII, the file name might be approximated, or encoded using the method of RFC 2231. But firefox is just sending 'filename' parameter encoded with the page encoding or the form accept-charset, this is, it is sending raw UTF-8 or the choosen encoding. Which is the reason for this?

All Replies (3)

Andrew
Andrew
  • Moderator
more options

Hello!

Thank you for inquiring about your issue on Mozilla Support! We appreciate your patience while we find an answer to your issue. At this moment I am escalating this to our advanced troubleshooting team who will assist you further in 24-48 hours.

Thank You!

Best Regards,

feer56

AliceWyman
AliceWyman
  • Moderator
more options

It would help answer your question if you could describe the issue better and how it is affecting your use of Firefox. For example, is the problem related to the following?

If you are not having a specific issue with using Firefox, you can

Here is a list of bugs with a comment mentioning rfc2388, in case it helps ... and here is another list of bugs mentioning rfc 2388 (with a space).

P.S. Before filing a bug report or adding a comment to a bug, please read https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines and https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

Endret av AliceWyman

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

If this is about your own website then try to ask advice at the MozillaZine "Web Development/Standards Evangelism" forum.

The helpers at that forum are more knowledgeable about web development issues.
You need to register at the MozillaZine forum site in order to post at that forum.