Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Replacing NetworkAccessManager features

    QtWebEngine
    1
    2
    1055
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      admoore last edited by

      I'm porting my (Python/PyQt) QtWebKit application to QtWebEngine. I used to do some things using the QNetworkAccessManager, but now that this is gone I can't find equivalents in QWebView or QWebPage.

      Specifically:

      • How do I set the proxy server and port?

      • How do I handle certificate errors?

      • How do I handle unsupported content (file downloads, e.g.)?

      Any help with these questions would be very appreciated.

      1 Reply Last reply Reply Quote 0
      • A
        admoore last edited by

        Well, for posterity, I'll answer my own questions as best I can:

        • Proxy server any port can be set in the OS environment ("http_proxy") and the widget seems to respect this setting.

        • override QtWebEnginePage.certificateError, which should return true if we're ignoring the error. Unfortunately the widget doesn't actually call this function for a lot of certificate errors, so it's not working right now.

        • File downloads aren't supported, maybe in 5.5

        tl;dr - QtWebEngine is very young, wait for future versions for it to be usable.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post