Hi,

PowerBuilder 2019 R3 does not support send header params along with the url while calling the navigate function! We will record it as a requirement in our CR pool and will transfer this enhancement to our product team for consideration.

Regards,
ZhaoKai

Didn't mean to hijack the thread but I am thinking this question may be related to the conversation here,

https://community.appeon.com/index.php/qna/q-a/pb-2019-r2-basic-authentication-and-new-webbrowser-control?errorcode=login_failed

In the old MS Web browser control, one can send header params along with the url while calling the navigate function. The way we implemented is by sending a Base64 encoded creds in the header param argument (last argument in the old navigate fn.).

With the new browser control, we can only send an endpoint to be navigated to without the option of sending a header param.

Wondering if this feature is implemented in 2019R3? The was a support ticket raised earlier for the same issue.

An authorization header is something you send, the browser control is for display.

Please explain what you need to accomplish, the browser control may not be the correct tool.

Hi Stanislav,

What is your actual usage scenario? Request to return a value or a page?

If it’s to return a value, please try using HTTPClient.
https://docs.appeon.com/pb2019r2/objects_and_controls/ch02s41.html

If it’s to return a page, PowerBuilder 2019 R3 will support basic and digest authentications. You can try with PowerBuilder 2019 R3 Beta and see if the current features can solve the issue.
https://docs.appeon.com/pb2019r3/whats_new/WebBrowser_enhancements.html

If the issue is not solved, please provide a detailed scenario for further analysis. Thanks!

Regards,
ZhaoKai