Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reply content does not work #114

Open
HansH opened this issue Apr 3, 2018 · 2 comments
Open

Reply content does not work #114

HansH opened this issue Apr 3, 2018 · 2 comments
Labels

Comments

@HansH
Copy link

HansH commented Apr 3, 2018

When using setReplyContent, this does not show up in the browser. For example, we can extend the facebookdemo by adding the following line to FBDemo::FBDemo

o2Facebook_->setReplyContent("You have succesfully authenticated to Facebook. ");

Expected behaviour:
After authenticating to Facebook, the browser displays the content "You have succesfully authenticated to Facebook."

Actual behaviour:
An empty page is shown. HTTP headers also do not seem to be received by the browser.

I tested this on MacOS High Sierra 10.13.3, using Firefox, Chromium and Safari. It also doesn't work when using a webview such as in the facebookexternalinterceptordemo.

Previously, I was on commit c0e33a8. It did work back then, but after pulling in all changes since then, it stopped working. I don't know which change/changes caused this problem.

@pipacs pipacs added the bug label Jul 30, 2018
@sykyck
Copy link

sykyck commented Aug 6, 2018

Yes I was also testing the code and found out that O2replyserver uses Qtcpsocket for server shouldn't it use QsslSocket the byte array that is passsed to parsequeryparams function in o2replyserver doesn't get the querytoken i believe its because the bytearray received is encrypted and needs to be decrypted with certificate

@niktischenko
Copy link

Should be fixed after #123 merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants