-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contrib of reference engine by nginx #5
Comments
The README has the full Nginx config, and tells you what to write where. Is that not working for you? |
All
|
I emailed this in a few hours back, but GitHub seems to have ignored the email. Re-posting via the web UI: On Mon, Sep 11, 2017 at 04:25:20AM +0000, xiekeyang wrote:
To support HTTP as well, you can drop the 301 from the example and use the example's HTTPS configuration instead.
This is not a valid image name, because Alternatively, you can use authority-based names like your _IP_V4_REGEXP = _re.compile(
'^' + _DEC_OCTET + '(\.' + _DEC_OCTET + '){3}(:[0-9]+)?$')
This is the DNS ancestor walk incorrectly treating your authority part as a FQDN. The
This far looks good to me, but if you aren't serving HTTPS on 8080 (see the
And this is your ref-engine hit dying because the URI said to use HTTPS, but your 8080 server doesn't support it. |
@wking , Yes it is my problem in configuration. It works correctly now on my local PC. |
So this issue is closeable? |
@wking
You seem have set up a reference engine by nginx and store some static page of ref-engine and cas-engine objects and debugged it. could you please submit them commit to
contrib
folder, or send to me? I'd debug on my local and implementgolang
client.The text was updated successfully, but these errors were encountered: