luccioman
commented
6 years ago Hello @vcarluer , sorry for the delayed answer, I wonder which YaCy proxy are you trying to use?
-
Transparent proxy : with "Transparent Proxy:" checkbox enabled in the /Settings_p.html?page=ProxyAccess page, and modifying your browser connection settings?
-
Or URL Proxy with "URL proxy" checkbox enabled in the /Settings_p.html?page=UrlProxyAccess page, browsing websites with URL such as http://yourpeer:yourport/proxy.html?url=http://externalurl/ ?
In transparent proxy mode, I am not sure how we could properly trigger indexing on https resources, as when opening SSL/TLS connections trough a transparent proxy, the proxy itself only "sees" a "tunnel" without access to plain-text data exchanged on it.
With the URL proxy mode, https resources can indeed trigger indexing even if you browse your peer trough http, but there are many other possible factors that can prevent any proxied resource to be indexed (cookies presence, cache rules...).
JeremyRand
Hello,
I had an issue while trying to set my pkcs12 certificate.
I have followed this: http://www.yacy-websuche.de/wiki/index.php/En:HOWTO_make_YaCy_allow_SSL_connections =>Using a CA Cert or other authority cert
To make it works I had to remove values for keyStore and keyStorePassword because there was an access denied issue on defaults/freeworldKeystore in logs.
It was set on port 8091. Now I can access https://MYDOMAIN:8091 and the connection is secured.
Bit I still cannot set my browser proxy for https on 8091 port: firefox says the connection is not secured. Only my http proxy on port 8090 works but it does not trigger crawling on https sites... So it is quite useless because most of them are on https.
If I try to configure https proxy on port 443 it disable itself in web gui (bug?). I can activate it again. But I have a SSL_ERROR_RX_RECORD_TOO_LONG error in firefox.
Don't know if all this is linked but you have all my tries to make it work! Help is welcome because https proxy automatic crawling is a great feature I think.
Thank you.