Possibly incorrect content type on access token response

[MaybeThisIsRu]

Hi folks,

I'm working on a Micropub client. A user who runs Known with indiepub is encountering an error using my app. Specifically, when their request was successful and I received a 200 OK response, the content-type header was set to application/x-www-form-urlencoded

As per the spec, I expected an application/json response.

Is what's available in the Token.php file correct?

indiepub/Pages/IndieAuth/Token.php

Line 67 in ed24711

header('Content-Type: application/x-www-form-urlencoded');

[MaybeThisIsRu]

Looks like someone opened a PR literally 5 hours ago! :)

#22

[scojjac]

When I attempted to add a Micropub client (in this case iA Writer) I received an 'Invalid Response' error, although my Known installation shows the client as authorized. I had a similar result when using the Indigenous client on iOS.

[MaybeThisIsRu]

@scojjac Consider opening a new issue as it sounds like your issue should have been fixed in https://github.com/idno/indiepub/releases/tag/0.9.12.

I'm no longer working on IndieWeb stuff, so I can't really say if your issue is a continuation of the original post.