When authorizing on many sites, the error is 301.
otter-browser-win32-weekly168 Win64
(https://picusha.net/img/2017-03/24/b3vfztye23o9n25hlkrbfvwns.png)
I confirm. Sometimes I've got it.
@ovas, @Freeman, any reliable way to reproduce it?
The error is not solved in 0.9.91-weekly169 :cry:
@ovas, it's hard to solve something that cannot be reliably reproduced. ;-)
BTW, you can try -xp version, it might be not affected.
I tested x32x64x XP, the result is the same.
(https://picusha.net/img/2017-03/30/usyw23qfo9s2cy47kjrkrka4y.png)
@ovas, I've done some initial testing with test page that creates such redirection and it works fine there...
Could you please try to reproduce it after setting interface language to English (in Help menu) and show output from Error Console too (Ctrl+Shift+O, and expand entry to show description of error)?
Scrin could do
(https://picusha.net/img/2017-03/31/jdtqi5g0mb6itp9wl5hmu2e3a.jpg)
(https://picusha.net/img/2017-03/31/zdil2v15z5kj876j1k63rw76l.jpg)
@ovas, thanks.
Are you using content blocking?
If yes then try to reproduce it after disabling it.
@ovas, 64 bit build of weekly 170 contains experimental change that might help with this issue, could you please test it?
The error has disappeared, but it is not possible to make autorization on many sites. v170x64
(https://picusha.net/img/2017-04/07/xj4zkq7yw2la54rb52xjabkox.jpg) (https://picusha.net/)
Error 301 exists in v170xXP
(https://picusha.net/img/2017-04/07/ytp5vxwpuy5hiymgl6r1zyapd.jpg) (https://picusha.net/)
I do not use the block
@ovas, I see, as noted only 64 bit version was patched.
Does it work fine with test-qtwebkit.exe?
How it works is normal, except for the problem of authorization on some sites.
@ovas, do you mean test-qtwebkit.exe or main executable?
The former is minimal test case that could be used to test such issues.
Good news everybody, I've identified what causes that issue and I'm testing fix which will be available in weekly 172.
@Emdek, when I try to open a non-standard link, I get 301 error. Build 172.
sourcetree://checkoutref?ref=default&cloneUrl=https://bitbucket.org/budden/yar&type=bitbucket
@Freeman, I see, I'll check that soonish.
@Freeman, uhm, it is sort of correct, but what would you suggest, some dialog asking what to do?
@Emdek, "Unknown protocol or URI type" error at least, common mechanism for external handlers in the future.
@Freeman, done, these errors will use custom header form now on.