Can we connect XML-Sitemaps on port 443?
« on: January 27, 2017, 12:47:12 PM »
Hi Support

We are using Standalone Sitemap Generator (PHP) v7.1.

Our host has enabled us to run the script by allowing internal connections to Port 80 through our firewall but reported 'if the script can be updated to connect on port 443, this would be optimal'.

Can I configure this in default.conf like this perhaps:-
<option name="xs_portconnection">443</option>

Or elsewhere?

Thanks
Pete



Re: Can we connect XML-Sitemaps on port 443?
« Reply #1 on: January 27, 2017, 06:31:27 PM »
Hello,

in case if your website is served via https protocol, 443 port is the default and there is no need to update the setting.
Re: Can we connect XML-Sitemaps on port 443?
« Reply #2 on: January 29, 2017, 08:15:45 AM »
Thank you

 
Re: Can we connect XML-Sitemaps on port 443?
« Reply #3 on: January 29, 2017, 09:29:02 PM »
I am a bit confused.

I am running the site on https.
The website's account is redirecting connections to my domain from port 80 to port 443.

If the server configurations are updated to 'allow local connections to the domain' the generator runs successfully. The web hosts have said that it would be optimal to connect on port 443.

If these configurations are reversed then I get the error.

~~
There was an error while retrieving the URL specified: (domain removed here)
HTTP Code:

HTTP headers:
x_csize: 0

HTTP output:
~~

Any suggestions would be appreciated.
Re: Can we connect XML-Sitemaps on port 443?
« Reply #4 on: January 30, 2017, 06:33:12 AM »
Hello,

sitemap generator always connects via port 443 for https by default. Please try to change "Use curl" setting in generator configuration.
Re: Can we connect XML-Sitemaps on port 443?
« Reply #5 on: January 30, 2017, 09:54:24 AM »
Thanks for your prompt help.

I already have 'Use curl' ticked.
And I have tried using the suggested IP Address too.
Re: Can we connect XML-Sitemaps on port 443?
« Reply #6 on: January 30, 2017, 06:49:46 PM »
Hello,

please let me know your generator URL/login in private message to check this.