You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have not had much time to look into this, but when the config_gophermap_omitserver option is set, the server and port are still written into the phlog post itself.
It does seem to work in gophermap at the top of config_dir_phlog at least.
This causes issues when the server needs to send a different port to different clients (e.g. gophernicus running with both plain gopher and gopher over TLS)
The text was updated successfully, but these errors were encountered:
I have not had much time to look into this, but when the config_gophermap_omitserver option is set, the server and port are still written into the phlog post itself.
It does seem to work in gophermap at the top of config_dir_phlog at least.
This causes issues when the server needs to send a different port to different clients (e.g. gophernicus running with both plain gopher and gopher over TLS)
The text was updated successfully, but these errors were encountered: