search

Tallefer / qtweb

Automatically exported from code.google.com/p/qtweb
0 stars 0 forks source link

Cookies does not saved over proxy #122

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use QTWEB over a proxy server (no private browsing nothing else just 
default settings)
2. You can not login into gmail - error cookies does not functioning
3.

What is the expected output? What do you see instead?
I expected the cooikies are saved but in the settings->privacy->cookies 
form I don't see any cookies nor before nor after trying login to gmail
The situation i exactly the same any other cookie based login service

What version of the product are you using? On what operating system?
QtWEB 3.2 build 15

Please provide any additional information below.
The gmail login page using https! The "simple" http pages saving cookies 
over proxy! I can see in settings->privacy->cookies form!
There is might be another important information. The proxy server address 
is an alternate domain name like something "web-proxy.abc.net" but the 
"real" name are something look like "domain.bastion.xyz.com"

Original issue reported on code.google.com by haraszti...@gmail.com on 5 Jan 2010 at 5:37

GoogleCodeExporter commented 9 years ago 
I have the same problem, if I enable socks proxy, I cannot login to (for 
example) facebook, 
if I dislable socks proxy, I can login without problems. Error message is 
"cookies must be 
enabled" or somenthing like this if socks is enabled.

Original comment by k...@vpnhosting.cz on 21 Apr 2010 at 10:29

GoogleCodeExporter commented 9 years ago 
having same problem with a lot of login page that need cookies.
=> With Sock5 tunnel nothing work, very boring.
example : gmail.
i hope this issues will be fixed soon, this make the browser quite unusefull: 
using portable browser without sock tunnel ? why ?... using a browser and being 
stock on login page ? => garbage!

Original comment by can...@gmail.com on 17 Jun 2010 at 4:27

GoogleCodeExporter commented 9 years ago 
same problem with http proxy. QtWeb v3.3.0.35

Original comment by benstone...@gmail.com on 13 Jul 2010 at 7:35

GoogleCodeExporter commented 9 years ago 
Same for 3.7.2 (build 081).

Original comment by roland.e...@gmail.com on 5 May 2011 at 11:59

GoogleCodeExporter commented 9 years ago 
Really too bad that this is still not fixed. QtWeb is useless for me (and 
others behind proxy).
This issue impact Sock and Http proxys.
Please fix this :-)

Original comment by ernest...@gmail.com on 18 May 2011 at 8:22

GoogleCodeExporter commented 9 years ago 
This is still an issue in the latest version.  Please fix it, the browser is 
great otherwise.

Original comment by west...@gmail.com on 21 Oct 2011 at 3:26

GoogleCodeExporter commented 9 years ago 
Same here.
v3.7.3 build 087

Original comment by thi...@thiagomt.com on 16 Jan 2012 at 7:55

GoogleCodeExporter commented 9 years ago 
same here! This is a really annoying bug

Original comment by akimbomi...@gmail.com on 22 Feb 2012 at 6:35

GoogleCodeExporter commented 9 years ago 
Seriously needs fixing

Original comment by jtorc...@gmail.com on 12 Mar 2012 at 11:40

GoogleCodeExporter commented 9 years ago 
Hi,

I would just like to add my support to this bugfix request.
Same problem with Yahoo and AOL - when logging in the site staes "your browser 
does not seem to be set to accept cookies"
Fault only occurs behind proxy at work.
I can log in to the same sites OK at home.

I'm not sure if it is connected, but there are several requests to manually 
accept SSL certificates when accessing the login page.  Sometimes QTWeb crashes 
at this point...

Original comment by martinre...@gmail.com on 4 Apr 2012 at 12:32

GoogleCodeExporter commented 9 years ago 
PS to my posting above:

I agree with others.  Apart from this one issue, the browser is great!

Original comment by martinre...@gmail.com on 4 Apr 2012 at 12:34

GoogleCodeExporter commented 9 years ago 
Would very much like to see this fixed. QTWeb 3.7.5 (Build 101) Portable.

Original comment by nymusic...@gmail.com on 23 Oct 2012 at 8:05

GoogleCodeExporter commented 9 years ago

Original comment by magis...@gmail.com on 26 May 2013 at 11:45

GoogleCodeExporter commented 9 years ago 
At least :-)
Happy to see you'll do something about this 3 years old bug ;-)
Thank you.

Original comment by ernest...@gmail.com on 26 May 2013 at 12:46

GoogleCodeExporter commented 9 years ago 
Looks like I've fixed this in my git repo. Fix would be available in the next 
release.

Original comment by magis...@gmail.com on 26 May 2013 at 11:25