search

google-code-backups / rsslounge

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

No login via SSL-Proxy #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. rsslounge is installed at rss.myserver.com (login via rss.myserver.com works)
2. do a login via https://ssl-account.com/rss.myserver.com

What is the expected output? What do you see instead?

The login page of rsslounge is displayed properly, but after giving 
name/password you get: https://ssl-account.com/?login=1 with "Bad Request - 
Your browser sent a request that this server could not understand." (Error 400)

I found no way to get around it anymore (see below). Maybe it's a security 
function for the login? Than it's maybe a solution to provide the alternative 
domain via config?

What version of the product are you using? On what operating system?

rsslounge 1.6
Mac PowerPC 10.4
Firefox 3.6.9

Please provide any additional information below.

This kind of works with rsslounge versions 1.3 - 1.5, after login you get a bad 
cookie-request warning like described, but pushing the back-button of the 
browser brings you into rsslounge via ssl-proxy. With 1.6. this doesn't work 
anymore.

(Background: It's a virtual webspace and the ssl-proxy is for free, I don't 
want to pay a hundred bucks for an own certificate and can't create my own one.)

Original issue reported on code.google.com by gegenglu...@googlemail.com on 14 Sep 2010 at 11:49

GoogleCodeExporter commented 8 years ago 
This issue appears because the proxy manipulates the global settings ($_SERVER) 
of php. I know this problem, because I use the same proxy. A workaround is, to 
set your domain name in the login template:
application/views/scripts/index/login.phtml

change line 28 from
<form method="post" action="<?PHP echo $this->url(); ?>?login=1">
to
<form method="post" action="rss.myserver.com/<?PHP echo $this->url(); 
?>?login=1">

I will not change the rsslounge code, because this is a issue of the ssl proxy.

Best regards
 Tobi

Original comment by zzuzzlwuzzl@googlemail.com on 2 Dec 2010 at 6:38

GoogleCodeExporter commented 8 years ago 
I still need to use the back-button after login in but besides this it works 
for me now. Thanks for getting back on this.

Original comment by gegenglu...@googlemail.com on 2 Dec 2010 at 11:12