A user has reported that GO names with dashes are mishandled:

I have a working configuration making use of GO endpoints, but problems
occur when trying to use a GO endpoint that has a hyphen like :

lsst#lsst–xfer

I've attempted to replace the hyphen in for example sites.xml with –

go://daues@lsst#lsst–xfer/scratch/daues

and this has lead to a hyphen inside the transfer job .in file :

"src_urls": [

{ "site_label": "inputxfer", "url": "go://daues@lsst#lsst–xfer/scratch/daues/f.a", "priority": 10 }

],

but the subsequent parsing seems to only obtain "lsst#lsst"

2017-01-18 20:04:24,904 INFO: 2017-01-18 20:04:24,480 INFO: Activating lsst#lsst
2017-01-18 20:04:24,869 CRITICAL: Unable to activate endpoint: : ClientError.NotFound (404 Not Found): No such endpoint 'lsst#lsst'
2017-01-18 20:04:24,869 CRITICAL: Please log into Globus Online and activate the endpoint there
2017-01-18 20:04:24,904 ERROR: Command exited with non-zero exit code (1): /usr/bin/pegasus-globus-online ...