After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777971 - Sites Login not working
Sites Login not working
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: General
3.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-01-31 08:47 UTC by Tasos K.
Modified: 2017-02-02 14:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tasos K. 2017-01-31 08:47:29 UTC
I am trying to login to my ebanking account (https://www.winbank.gr/sites/idiwtes/en/Pages/default.aspx), the site accepts my user/pass - no error indication - but after loading the page, it presents me with the same login page.
Comment 1 Sergio Villar 2017-01-31 09:04:20 UTC
Does it work with any other browser?
Comment 2 Tasos K. 2017-01-31 11:15:42 UTC
Yes, I also have Firefox installed on the same system and it works without problem.
Comment 3 Michael Catanzaro 2017-01-31 18:01:39 UTC
Any errors in the web inspector?

It's *possible* this is an Epiphany problem, but it's really, really unlikely, so I'm going to direct you to WebKit Bugzilla instead. Note that problems like these are not normally debugged by WebKit developers unless the website developers assist:

Thanks for taking the time to report this.
This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.
Comment 4 Tasos K. 2017-02-01 08:20:23 UTC
To tell the truth I don't quite get the Web Inspectors output, but the only error I get is :

[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (print.css.map, line 0).

Anyway, I'll report a bug in Webkit, thank you very much for your answer.
Comment 5 Michael Catanzaro 2017-02-02 14:53:10 UTC
Oh one more thing we should check: try disabling the adblocker in the preferences dialog, to be sure that's not causing it.