Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Serving seafile behind https reverse proxy #34

Closed
orymate opened this issue Apr 14, 2013 · 1 comment
Closed

Serving seafile behind https reverse proxy #34

orymate opened this issue Apr 14, 2013 · 1 comment

Comments

@orymate
Copy link
Contributor

orymate commented Apr 14, 2013

I found out, that my problem described in #29 was totally unrelated to IPv6.

It is with Chrome silently blocking mixed content (ie. http ajax request to localhost from seafile served on https). The trivial solution would be if ccnet also listened for https requests. Do you have any other idea for resolving this?
@freeplant
Copy link
Member

In current implementation, if the http request is blocked, a error will be shown with a link for users to click. Listen on https is not possible for the local web (requires https CA) and having the server to check both http and https is not good.

One solution is to config the client checking page to http.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@freeplant @orymate