1

I´m using the CEF TChromium component and I´m seeing that Chromium is doing some stuff with the HTTP headers. I´ve seen this is an open issue in the CEF project.

My problem is that this "Provisional headers" sent by the browser don´t have a session cookie.

Is there a way to tell Chromium not to strip the request headers?

Héctor C.
  • 433
  • 4
  • 17
  • 1
    The linked issue is about DevTools not refreshing the view after a request is sent. While DevTools displays it incorrectly, CEF is sending a different (perhaps correct) set of cookies. How do you know that the browser doesn't send a session cookie? – Sergey Avdeev Oct 12 '17 at 05:38
  • 1
    I don´t (and can´t) because I´m connecting to some external server over https, so I can´t see what the real traffic is. – Héctor C. Oct 17 '17 at 16:59
  • 1
    Have you tried navigating to that server in Chrome and checking that it sends the session cookie using DevTools? – Sergey Avdeev Oct 17 '17 at 19:50
  • 1
    Yeah, tried that in Chrome and other browsers and the server sets a cookie after a login event. – Héctor C. Oct 18 '17 at 10:53
  • 1
    In you CEF application can you see that the server is sending that same cookie after the login event? – Sergey Avdeev Oct 18 '17 at 22:27
  • 1
    Hi, Sergey, I solved the issue. It was about the HTTP headers I was sending but not the cookies, it was a problem of the server dropping requests because of the User-Agent. I changed the user agent to an accepted one and it worked. – Héctor C. Oct 24 '17 at 14:06
  • 1
    Nice. It sounds like CEF TChromium was not a problem after all. – Sergey Avdeev Oct 24 '17 at 20:17

0 Answers0