cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
degvalentine
Level 8

HTTP action broken by Content-Type `text/html; charset="utf-8"`

The HTTP action fails to parse the Content-Type header of a response if it contains a quoted charset subtype.

 

content-type: text/html; charset="utf-8"

 

According to RFC7231 Section 3.1.1.1, it is valid to have quotes around a subtype, such as charset.

 

I created a simple example Flow to illustrate the point.

 

2018-11-08 12_06_48-Edit your flow _ Microsoft Flow.png

 

Here's the response in the triggering Flow's HTTP action:

 

{
  "error": {
    "code": "BadRequest",
    "message": "The provided input content is not valid: 'The provided content-type character set '\"utf-8\"' is not valid. Please use a Unicode character set such as UTF-8 or ASCII character set.'."
  }
}

Another example showing a request to GET a Facebook post webpage (not through their Graph API):

 

2018-11-08 12_12_36-Run History _ Microsoft Flow.png

 

Will the Flow team implement support for quoted content subtypes?

2 REPLIES 2
Community Support Team
Community Support Team

Re: HTTP action broken by Content-Type `text/html; charset="utf-8"`

Hi @degvalentine,

 

From the error message, it seems that the provided content type character set utf-8 has not been supported yet.

If you need a support for quoted content subtypes, please submit your idea on Flow Ideas Forum at here:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
degvalentine
Level 8

Re: HTTP action broken by Content-Type `text/html; charset="utf-8"`

Mabel,

 

Names for character encodings are case-insensitive, so "utf-8" and "UTF-8" are identical. This isn't about charset support, just about header parsing.

 

You can see it in the error message where is effectively says "utf-8 isn't valid, please choose UTF-8".

...character set '\"utf-8\"' is not valid. Please use a Unicode character set such as UTF-8...

 

Do you mean you believe the header parsing intentionally didn't support the full spec and should be treated as a new feature instead of a bug?

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

firstImage

Incoming: New and improved badges!

We've given our badges an overhaul and also added some brand new ones!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Kudoed Authors
Users Online
Currently online: 335 members 5,866 guests
Please welcome our newest community members: