Do all server actions use encType="multipart/form-data"?

[bestickley]

Summary

Do all server actions use encType="multipart/form-data"? Do any use encType="application/x-www-form-urlencoded"?

Additional information

No response

Example

No response

[icyJoseph]

Interesting question. I have explored that server actions use a text plain content type, and multipart/form-data, more over I found this bit in the React codebase:

• https://github.com/facebook/react/blob/efb22d8850382c3b53c1b2b8d22036d7e6cc9488/packages/react-dom-bindings/src/client/ReactDOMComponent.js#L132-L137

          console.error(
            'Cannot specify a encType or method for a form that specifies a ' +
              'function as the action. React provides those automatically. ' +
              'They will get overridden.',
          );

So, specifying that, is not gonna do it. I also though of calling the server action manually, with URLSearchParams, but that goes the plain text road...

Just throwing this other file in, where some serialization happens, https://github.com/facebook/react/blob/3644f0bd214b7c08a522cc9212dfca902777bf8c/packages/react-client/src/ReactFlightReplyClient.js#L117-L120

Do you have a specific use case in mind?

[bestickley]

@icyJoseph, thank you for the well thought out response! Yes I do. I'm building cdklabs/cdk-nextjs. The infrastructure used to deploy Next.js requires a x-amz-content-sha256 header to be set with hash of body before any POST request so I needed to get access to the server actions body in order to create hash. See cdklabs/cdk-nextjs#87. I've resolved the issue by creating the raw multipart/form-data body myself (not using default browser version) since I need access to it to create hash. You can see code here in case you're curious.