Literal word "text" does not work, you must use "text/plain"

[RayDeanTech]

I'm supporting a "legacy" jQuery application. Notice in the screenshot that the contentType is the literal word text as opposed to text/plain.

I tried changing the type for the built-in Express body parsers to see if that would fix the problem, but no.... the only way for the built-in parsers to see the payload is if contentType in the AJAX post is set to text/plain.

Here's my problem: we are testing the transition away from a Java Servlet to Node, so I want to leave the jQuery code UNMODIFIED to the fullest extent possible.

Is there anyway that I can get Express to "force" the interpretation of this payload as "text/plain" without having to change the contentType?

[dougwilson]

Hi @NamedArray , what is the content-type header set to currently that is coming in? If just the word text, you need to just use the function value of the type parameter, since the string parameter only accepts valid mime types.

[RayDeanTech]

@dougwilson Is that where I should/could process the req.body in this particular circumstance?

You know, I went for a jog. I don't think the Boss will have too much of an issue with changing his posting code to text/plain, I think I'm being pedantic.

So, I started doing this:

app.use(express.text({
    type: function(req) {
        if (req.is('text')) {
            // change the content-type header?
            // ...OR process the req.body
        }
    },

I'm pretty sure I've posted various other content types to the old endpoint... so, anyway, if something goes awry, at least we have that type function option :)

[dougwilson]

In the type function you can perform any logic you want to decide if body parser should read the body. Return true if you want to, false if not. Your logic could be as simple as return req.headers['content-type'] === 'text' based on your description.