Closed daveof closed 13 years ago
Ah yes, those query string parameters should definitely be encoded. I just pushed a patch to github and to the play module repository.
Thanks for the bug report!
I just got this in fbconnect-0.3:
Caused by: java.net.URISyntaxException: Illegal character in query at index 240: https://graph.facebook.com/oauth/access_token?client_id=184868531547213&redirect_uri=http://local.rank.my:9000/fbconnect/oauth/callback&client_secret=738fd21f012d3a7cb40e379663590c5f&code=2.p2BLC_MSHVvo9N5EeFq_bA__.3600.1296691200-534496019|Hf_Dar_LB0zLVgwHrMkLFC3bA0g
at java.net.URI$Parser.fail(URI.java:2809)
at java.net.URI$Parser.checkChars(URI.java:2982)
at java.net.URI$Parser.parseHierarchical(URI.java:3072)
at java.net.URI$Parser.parse(URI.java:3014)
at java.net.URI.<init>(URI.java:578)
at java.net.URI.create(URI.java:840)
Shouldn't it be fixed in that version?
Same here, got this error with latest version from play module repo.
I did a quick hack to solve this issue and sent an pull request to murz.
Hey guys, I just pushed a version that builds the URLs in a different way. Everything should be properly encoded - can one of you pull down the latest and confirm?
https://github.com/murz/play-fbconnect/commit/095e24e1b140603f526a2b1842e206e1a52b61cc
It looks like this is actually a bug with Play's WS
class. It should be fixed soon because all they need to do is upgrade a dependency.
You can follow the ticket here: http://play.lighthouseapp.com/projects/57987/tickets/582-async-http-client-140-and-javaneturisyntaxexception#ticket-582-1
And there is some discussion about it on the google group: http://groups.google.com/group/play-framework/browse_thread/thread/974616c47fcca672
I am having a problem connecting to Facebook because my client_secret parameter contains a pipe character (|). The line String response = WS.url(authUrl).get().getString(); generates an exception