1.3.4 - added alternative HTTP 403 response

42 views
Skip to first unread message

claudio.casoli

unread,
Apr 2, 2012, 7:09:23 AM4/2/12
to rhod...@googlegroups.com
I saw in the newest version this new feature:
 - added alternative HTTP 403 response when client failed to authenticate. Helps solving issues with Mercurial and LDAP

How could I  configure this feature in my installation? I didn't found any example in the documentation.

Thank you for any help you can provide, and thank you for the nice project

Marcin Kuzminski

unread,
Apr 2, 2012, 5:43:21 PM4/2/12
to rhod...@googlegroups.com
It's setup in the .ini file.


see -> https://secure.rhodecode.org/rhodecode/files/ee07357d9265e5b41bf78ea709a1a7c46d5d9c1e/production.ini#L96-99

claudio.casoli

unread,
Apr 4, 2012, 7:10:08 AM4/4/12
to rhod...@googlegroups.com
Hi Marcin,
   I've setup my .ini file. Now when I pull or push my repo with tortoiseHg (or with the eclipse hg plugin) I recieve always 403. Both clients don't asked me the password.
Should I to pull or push my repo by command line?

Thanks for all,
   Best regards Claudio

Marcin Kuzminski

unread,
Apr 4, 2012, 5:55:29 PM4/4/12
to rhod...@googlegroups.com
Returning different than expected return code probably breaks those clients, and they only issue password prompt for 401 ret code (which makes sense). So either you somehow configure them to send password always, or use console client(but still that will not ask password)

claudio.casoli

unread,
Apr 5, 2012, 5:46:26 AM4/5/12
to rhod...@googlegroups.com
Thank's for your support.
Reply all
Reply to author
Forward
0 new messages