X2Go Bug report logs - #1446
Domain name issues with client 4.1.2.2 when using HTTP broker

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: Mark Hymers <mark.hymers@ynic.york.ac.uk>

To: submit@bugs.x2go.org

Subject: Domain name issues with client 4.1.2.2 when using HTTP broker

Date: Thu, 19 Mar 2020 20:03:00 +0000

[Message part 1 (text/plain, inline)]

Package: x2goclient
Version: 4.1.2.2


Hi,

We have an x2go deployment using the HTTP broker and multiple backend 
x2go servers.

We have found that if users use 4.1.2.2, when sessions are resumed the 
system tries to connect to the hostname without the domainname attached. 
  I.e. system1 instead of system1.example.org.  This is not a problem 
with 4.1.2.1 or earlier client releases (no server changes were made).

I have tracked this down to a change in session handling in 
resumeSession in src/httpbrokerclient.cpp.

In this function, config->serverIp is set to server which, at this point 
only contains the hostname, not the FQDN.  config->serverIp has already 
been set at this point by the parseSession function on line 700 (current 
git HEAD):

config->serverIp=words[0];

This version of config->serverIp is the proper FQDN.

To fix this, I just removed the overriding of serverIp in the 
resumeSession function (see attached patch) but I'm not sure if this is 
fully correct; presumably there was a reason for setting it in 
resumeSession.

Thanks,

Mark

-- 
Mark Hymers, Lecturer in Neuroimaging Methods
York NeuroImaging Centre and Department of Psychology
University of York, UK

Please note that my email address is: mark.hymers@ynic.york.ac.uk
Responses to messages sent to other addresses may be delayed

[x2goclient_fix_server_name.diff (text/x-patch, attachment)]

Send a report that this bug log contains spam.