GetPostSelf having issues with long posts

[aldarisbm]

Using the current GetPostSelf I've run into problems when sending large (over 6k chars) payloads since payloads get encoded and added to the URL. I've run into two different times where this has raised an issue.

Once just a random 400 error (reproducible) and the second time -with a larger payload- it gave me a 414 URI too long error (reproducible as well)

This could be fixed by sending the body in the actual body of the request.

I've started some changes here that should be non-breaking, but would like to know if you're also working on something like this?

[turnage]

I am not. Your changes would be welcome, thank you for asking!

Vào CN, 26 thg 7, 2020 lúc 12:03 CH Jose Berrio [email protected] đã viết:

Using the current GetPostSelf I've run into problems when sending large (over 6k chars) payloads since they get encoded and added to the URL. I've run into two different times where this has raised an issue.

Once just a random 400 error (reproducible) and the second time -with a larger payload- it gave me a 414 URI too long error (reproducible as well)

This could be fixed by sending the body in the actual body of the request.

I've started some changes here that should be non-breaking, but would like to know if you're also working on something like this?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/turnage/graw/issues/80, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWR64BO5NARXUARU4INQJDR5RHVFANCNFSM4PIBLQMQ .