Mystring.split(environment.newline) fails between windows and linux

Question

0.00/5 (No votes)

See more:

Hi all,

I've recently migrated a web app from a Windows Azure App Service to a Linux one.
I'm now running into a problem that I had not anticipated.
Since I'm new to running on Linux I thought I'd ask here.

So basically the web app allows users to upload a text file and the web app then sends the text to a web service running on Windows for further processing.

Here's the gist of it:

C#

string content = await IFormFile.ReadAsStringAsync();

// Some code here, client is an HttpClient.

string json = JsonConvert.SerializeObject(new { content, something, somethingElse });
var httpcontent = new StringContent(json, Encoding.UTF8, MediaTypeNames.Application.Json);
using HttpResponseMessage response = await client.PostAsync("MyEndpoint", httpcontent).ConfigureAwait(false);

// Later in MyEndpoint...
var lines = content.Split(Environment.NewLine);

I'd expected Split(Environment.NewLine) would return hundreds of lines, but I'm getting only one when I call the endpoint from the Linux web app.
My guess is that Linux sends the new lines as \n while Windows uses \r\n.

I'd had hoped the JSON would serialize to \n and then the service on Windows would deserialize it as \r\n.

I've probably used plenty services running on Linux and I've never had to worry about my new lines.
I don't want to know what my service runs on and adjust my new lines accordingly.
What am I doing wrong?

The web app uses .NET8 and the web service uses .NET6. Both are running in Azure Web Apps.

What I have tried:

Plenty of logging to find the problem.
I know of workarounds, like splitting in the Linux app and then sending the lines to Windows, or splitting on \n instead of Environment.NewLine.
Did some googling, but couldn't find an actual answer to my problem.

Posted 28-Feb-24 1:36am

Sander Rossel

Add a Solution

Comments

PIEBALDconsult 28-Feb-24 10:01am

I wrote my own tokenizer for that. I wouldn't use Split except in very simple cases.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Accepted Answer · 2024-02-28T03:38:00

Since you're using .NET 6, you could try using the MemoryExtensions.EnumerateLines method[^] method, which should handle both Windows and Linux newlines for you.

C#

List<string> lines = [];
foreach (ReadOnlySpan<char> line in content.AsSpan().EnumerateLines())
{
    lines.Add(line.ToString());
    // Or process the line here without creating a string, to avoid the allocation...
}

Or you could try the String.ReplaceLineEndings method[^], although that would allocate a new string.

Quote:
The list of recognized newline sequences is CR (U+000D), LF (U+000A), CRLF (U+000D U+000A), NEL (U+0085), LS (U+2028), FF (U+000C), and PS (U+2029). This list is given by the Unicode Standard, Sec. 5.8, Recommendation R4 and Table 5-2.