On Wed, Jul 19, 2017 at 1:54 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:On Wed, Jul 19, 2017 at 6:16 PM, Khushboo Vashi <khushboo.vashi@enterprisedb.com> wrote:On Wed, Jul 19, 2017 at 6:10 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:Okay, I think this is a bug with 1.6.Found similar issue: https://redmine.postgresql.org/issues/2563 So, as per this RM information, you can change the WSGIScriptAlias from /pgadmin4 to / to fix this issue.Yes, This is a work around.But we also have to fix this issue at code level to honour the virtual DirectoryRoot path :)Are you working on this Murtuza? I don't want it to get forgotten. -- Dave PageBlog: http://pgsnake.blogspot.comTwitter: @pgsnakeEnterpriseDB UK: http://www.enterprisedb.comThe Enterprise PostgreSQL Company
On Wed, Jul 19, 2017 at 6:16 PM, Khushboo Vashi <khushboo.vashi@enterprisedb.com> wrote:On Wed, Jul 19, 2017 at 6:10 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:Okay, I think this is a bug with 1.6.Found similar issue: https://redmine.postgresql.org/issues/2563 So, as per this RM information, you can change the WSGIScriptAlias from /pgadmin4 to / to fix this issue.Yes, This is a work around.But we also have to fix this issue at code level to honour the virtual DirectoryRoot path :)
On Wed, Jul 19, 2017 at 6:10 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:Okay, I think this is a bug with 1.6.Found similar issue: https://redmine.postgresql.org/issues/2563 So, as per this RM information, you can change the WSGIScriptAlias from /pgadmin4 to / to fix this issue.
Okay, I think this is a bug with 1.6.Found similar issue: https://redmine.postgresql.org/issues/2563
pgadmin-support by date:
Соглашаюсь с условиями обработки персональных данных
