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.

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

Firefox says search page is not secure #253

Closed
noumar opened this issue Apr 11, 2014 · 5 comments
Closed

Firefox says search page is not secure #253

noumar opened this issue Apr 11, 2014 · 5 comments
Assignees

Comments

@noumar
Copy link
Contributor

noumar commented Apr 11, 2014

Firefox complains/warns about the /search page not being secure when using HTTPS.
"Connection Partially Encrypted" ... "contains unencrypted elements".

Looking at the source code this seems to be because of icon images using HTTP. The URLs should be changed to relative.

@noumar noumar added this to the 0.5 – Spring release milestone Apr 11, 2014
@noumar noumar self-assigned this Apr 11, 2014
@emanueldima
Copy link
Contributor

Could be the images fixed on this commit: fec9a7c?

@noumar
Copy link
Contributor Author

noumar commented Apr 11, 2014

Yes. You are right. Hadn't pulled that commit yet. Closing as invalid since already fixed in #213.

@noumar noumar closed this as completed Apr 11, 2014
@noumar
Copy link
Contributor Author

noumar commented Apr 11, 2014

Still appears on my VM after pulling in the changes and deploying. @emanueldima can you verify this on your VM?
Firefox still complains and "curl -sk https://VM-IP/search | grep -i 'http:'" shows both <a> and <img> tags referring to HTTP URLs.

@noumar noumar reopened this Apr 11, 2014
@emanueldima
Copy link
Contributor

Indeed, my Chrome also reports the same problem. I suspect it's because the html snippet for each record is cached (if I'm not wrong it's in the database, table bibfmt) and keeps the old img references. I don't know whether this cache is refreshed if we delete it.

@noumar noumar removed the invalid label Apr 14, 2014
@noumar
Copy link
Contributor Author

noumar commented Apr 17, 2014

The bibfmt cache can be emptied by running "inveniomanage bibformat expunge". This needs to be done for all old records generated before #213 fix was applied. @llehtine can you please do this on test-server so we can see the results.

@noumar noumar closed this as completed Apr 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants