Bug #2371

SOGo redirect to internal DNS name

Added by Davide Principi about 6 years ago. Updated almost 6 years ago.

Status:CLOSEDStart date:11/27/2013
Priority:NormalDue date:11/27/2013
Assignee:-% Done:

100%

Category:nethserver-sogo
Target version:v6.5-beta3
Security class: Resolution:
Affected version:v6.4-beta2 NEEDINFO:No

Description

The URL

  http://public.domain.name/sogo

where public.domain.name is resolved by a public DNS or is a public IP address, is redirected to
  https://internal.domain.name/SOGo

where internal.domain.name is resolved by the green network DNS. We expect it remains "public":
  https://public.domain.name/SOGo


Related issues

Related to NethServer 6 - Enhancement #2758: Preserve IP host name in HTTP requests CLOSED
Related to NethServer 6 - Enhancement #2759: Preserve request host name in SOGo CLOSED

Associated revisions

Revision cd205372
Added by Davide Principi about 6 years ago

Expose SOGo through custom virtual hosts. Refs #2371

Any hostname listed in sogod/VirtualHosts prop is expanded to an
Apache virtual host configuration. The default host name is always
added to the list.

History

#1 Updated by Davide Principi about 6 years ago

  • Due date set to 11/27/2013
  • Status changed from TRIAGED to ON_DEV
  • Assignee set to Davide Principi
  • Start date set to 11/27/2013
  • % Done changed from 20 to 30

#2 Updated by Davide Principi about 6 years ago

  • Status changed from ON_DEV to MODIFIED
  • Assignee deleted (Davide Principi)
  • % Done changed from 30 to 60

MODIFIED

Added an httpd.conf template fragment that set SogoStatus=enabled on any virtual host listed in sogod/VirtualHosts prop.

See also Access SOGo from the public network.

Test case

By default SOGo is configured on the default virtualhost only.

  • Create mycorp.tld server alias in Hosts UI module
  • Enable SOGo for it:
        # config setprop sogod VirtualHosts mycorp.tld
        # expand-template /etc/httpd/conf/httpd.conf
        # service httpd graceful
    

Now SOGo is exposed at https://mycorp.tld/SOGo:

    # curl -k -v -L http://mycorp.tld/sogo
...301 => 302 => 200 OK

#3 Updated by Davide Principi about 6 years ago

  • Status changed from MODIFIED to ON_QA
  • % Done changed from 60 to 70

In nethserver-testing:
nethserver-sogo-1.2.1-3.0gitcd205372.ns6.noarch.rpm

#4 Updated by Giacomo Sanchietti almost 6 years ago

  • Assignee set to Giacomo Sanchietti

#5 Updated by Giacomo Sanchietti almost 6 years ago

  • Status changed from ON_QA to VERIFIED
  • Assignee deleted (Giacomo Sanchietti)
  • % Done changed from 70 to 90

Tried to access using ip address before property configuration: httpd daemon redirects to FQDN.

After configuration:

config setprop sogod VirtualHosts 192.168.1.1
signal-event nethserver-sogo-update 

SOGo is now accessible also using ip address.

Marking as VERIFIED

#6 Updated by Davide Principi almost 6 years ago

  • Status changed from VERIFIED to CLOSED
  • % Done changed from 90 to 100

In nethserver-updates:
nethserver-sogo-1.2.2-1.ns6.noarch.rpm

#7 Updated by Davide Principi over 5 years ago

#8 Updated by Davide Principi over 5 years ago

Also available in: Atom PDF