@Reporter: Could you please provide a sample test file/URL which would help ET team to triage the issue in a better way.

Thanks!

A test file can be found attached to this e-mail.

That said, I looked at the source code, and it seems that the 
troublesome line is line 211 of 'FormData.cpp' 
<https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/html/forms/FormData.cpp?l=211>.  
Here, `NormalizeLineEndingstoCRLF` is being called.  It seems to me that 
probably nothing should be called to change the contents of the string.  
I think that, no matter how you try to normalize the line endings, 
you're going to end up changing the string in ways that are surprising 
to people (and were surprising to me, when I sent a string through 
`FormData`, got it back from the server, and puzzled over trying to 
figure out why it didn't have identity with the one that I sent).  I 
would think it's better just to leave them alone.  This is what Firefox 
seems to be doing, at least with regards to CR and LF.

If we agree that this is a bug and have a clear idea of what the 
solution is, I'm happy to implement and submit the fix, myself.

On 12/29/2017 6:00 AM, vamshi.k… via monorail wrote:

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Adding Blink>Network>XHR to the component list, FormData is defined there.

I'm also confirming the bug. I don't see anything about this in the spec, and neither Gecko nor WebKit seem to do this CRLF conversion.

Both of FormData.append() and built-in form control elements use the same append() implementation. We should have two versions; one for FormData.append(), which doesn't normalize string data [1], and another for built-in form controls, which does normalize string data [2].

[1] https://xhr.spec.whatwg.org/#dom-formdata-append
[2] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#append-an-entry

i will take this issue.

Hi hs1217@

I'm already working on this and patch was ready, I will upload it later today

And seems both Gecko and Webkit not following the spec do the CRLF convert when appending form control name and value to form data

If you are not started on this issue (I hope)
Could you let me take it?

Thanks

@ratsunny
i started to make patch but i'm fine.
i would like to assign this issue to you instead of me.
but Issue owner must be a project member in this system.
so i can't assign this issue to you.
anyway i will quit to make patch.
please keep doing.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/38968451310754c3481dc465631ca3988554497a

commit 38968451310754c3481dc465631ca3988554497a
Author: Sunny <ratsunny@gmail.com>
Date: Wed Jun 13 04:51:57 2018

Align FormData CRLF normalization behavior with standards

According to xhr spec[1], no CRLF normalize operation need to be
performed when invoking FormData methods, so all normalization
call is removed in this commit.

But in form sepc[2], when appending data from form controls to
FormData, both name and value should be normalized. New methods
|FormData::AppendFromElement| will perform the normalize operation.

[1] https://xhr.spec.whatwg.org/#dom-formdata-append
[2] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#append-an-entry

BUG= 798030 

Change-Id: If90a8e500705013c2935e5290624d4414dd32a72
Reviewed-on: https://chromium-review.googlesource.com/1091238
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566723}
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/WebKit/LayoutTests/http/tests/local/formdata/formdata-methods.html
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/base_checkable_input_type.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/file_input_type.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/form_data.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/form_data.h
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/form_data_test.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/hidden_input_type.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/html_button_element.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/html_select_element.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/html_text_area_element.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/image_input_type.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/input_type.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/submit_input_type.cc
[modify] https://crrev.com/38968451310754c3481dc465631ca3988554497a/third_party/blink/renderer/core/html/forms/text_field_input_type.cc

A great thanks to @hs1217 and @tkent
I believe this issue could marked as "Fixed" now