Github user loachli commented on the pull request:
https://github.com/apache/spark/pull/2102#issuecomment-53170070
hey @pwendell , thanks for your comments- Yes, my proxy support https.
I had used no-proxy open environment before. In order to support more
people using spark, I have to move spark environment into my company's inner
environment. For security reason, I have to use http-proxy provided by my
company to access network.
When I used spark in my company's inner environment, I could not compile
spark successfully.
Because the maven's error hit was not obvious, I spent much time solving
this problem.
You can find the definition of these two parameters in
http://maven.apache.org/wagon/wagon-providers/wagon-http/
"maven.wagon.http.ssl.insecure = true/false (default false),
enable/disable use of relaxed ssl check for user generated certificates.
maven.wagon.http.ssl.allowall = true/false (default false),
enable/disable match of the server's X.509 certificate with hostname. If
disabled, a browser like check will be used."
I also found someone else had met this issue
(https://issues.apache.org/jira/browse/SPARK-1125)
So I believe, this issue will be met by others in the future.
I still think we could add this hit to the document. One optional way is
that I could add risk warnig when using these parameters. Do you agree?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
