René Ullrich - Thank you for bringing this up. We are on the same boat as well. We send a Base 64 Encoded credential on the old MS web browser control and there is no way to do that in 2019 R2 yet.
Chris, really appreciate, if you have an update on this ticket.
Hi Balu ... It's now on Engineering's ToDo list but no commitment from them yet as to when. Appeon is super busy in the background rolling out PB2019 R2 this week and next. So I suspect that Engineering has not even a chance to look at this yet. They will be reviewing all these enhancement requests shortly and will then decide what features / enhancements that will be doing for PB2019 R3. I suspect that any updating (communication) about your enhancement will be through the ticket system. Also ATM, I have no date for R3 (just in case you were going to ask about that next).
I do not believe that this is currently supported. Please create a PB2019 R2 beta Support Ticket outlining this deficiency so that Appeon Engineering can address this issue. You have a good point.
Regards ... Chris
I saw your ticket today and transferred it to Engineering. I do not believe that the R2 version of the control has this capability. However, it does not mean that the next January beta might not. Let's see how Engineering responds to your question as they know the upcoming features that are currently not in the R2 beta "preview" release.
Since it is based on Chromium, it will be compatible with the Chrome browser.
For your specific question about headers, I'm not sure what that has to do with the upcoming browser control, that is something usually done when calling a web service via HTTPClient.
if I try to call a webpage that requires basic authentication with the new webbrowser control I get back a 401 (Unauthorized) page because of missing basic authentication. (Microsoft Webbrowser control shows a dialog to enter the credentials is this case.)
I want to specify the credentials anyway programmatically so I can access the website using the new browser control.