Op 20-4-2016 om 22:38 schreef Shawn Heisey:
It will be accessible from the Internet, but as long as nobody ever
knows what the URL path is, that should be OK.
You could put the stats in a separate backend and use a acl to verify
proper source subnet/ip is requesting it.
Add some user+password
On 4/20/2016 12:56 PM, PiBa-NL wrote:
> Op 20-4-2016 om 20:45 schreef Shawn Heisey:
>> The problem is that if I try to go tohttp://spark.REDACTED.com:8080/
>> ... this is redirected tohttps://spark.REDACTED.com:8080/ ... and I get
>> this in the log:
> Are you using HSTS on that domain name?
>
you have stats bound to all interfaces, all addresses on port 8080.
so when your spark redirect sends you to "8080" you get stats instead
of what you expect.
There are 2 options here, really. #1) Fix your spark app config,
to stop trying to redirect you to a specific port.
#2) Have your
Op 20-4-2016 om 20:45 schreef Shawn Heisey:
The problem is that if I try to go tohttp://spark.REDACTED.com:8080/
... this is redirected tohttps://spark.REDACTED.com:8080/ ... and I get
this in the log:
Are you using HSTS on that domain name?
Can you check the networking tab of firebug/chrome
I have this in my config:
listen stats 0.0.0.0:8080
description The stats listener.
stats uri /
Elsewhere in my config I have something that will redirect http requests
to the hostname spark.REDACTED.com over to https, which is not anything
unusual. The IP address for this
5 matches
Mail list logo
