Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
litespeed_wiki:config:real-time-stats [2017/12/20 15:59] Jackson Zhang |
litespeed_wiki:config:real-time-stats [2018/03/14 15:17] Jackson Zhang |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| Since 5.2 we started forcing SSL so unless you forced disable SSL for admin menu you will want to force it at HTTPS and end in -k if it is a self-signed certificate. If you still run http instead of https, you may experience 403 error. | Since 5.2 we started forcing SSL so unless you forced disable SSL for admin menu you will want to force it at HTTPS and end in -k if it is a self-signed certificate. If you still run http instead of https, you may experience 403 error. | ||
| - | curl -i -u username:password https://localhost:7080/status?rpt=detail -k | + | curl -i -k -u username:password https://localhost:7080/status?rpt=detail |
| - | curl -i -u username:password https://localhost:7080/status?rpt=summary -k | + | curl -i -k -u username:password https://localhost:7080/status?rpt=summary |
| | | ||
| For ''/status'' query, only 127.0.0.1 (localhost) was allowed before. Starting from 5.2.3, a new feature has been added to allow query from trusted IP set through Apache httpd.conf at server level. The native server level access control trusted IP does not work. You have to use Apache style config like the following: | For ''/status'' query, only 127.0.0.1 (localhost) was allowed before. Starting from 5.2.3, a new feature has been added to allow query from trusted IP set through Apache httpd.conf at server level. The native server level access control trusted IP does not work. You have to use Apache style config like the following: | ||