|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-14223) accessing Jenkins through https produces browser warning about mixed https/http content
di...@fast.au.fujitsu.com (JIRA) Wed, 27 Jun 2012 01:21:23 -0700
- [JIRA] (JENKINS-14223) accessing Jenkins ... di...@fast.au.fujitsu.com (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... di...@fast.au.fujitsu.com (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... ohtake_tomoh...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... di...@fast.au.fujitsu.com (JIRA)
I haven't changed that parameter (still set to http://localhost:9080/jenkins/) as I want to keep it available at that location when accessing it on the machine itself.
loadScript is not pointing to my localhost, but you're saying it picks the protocol from the Jenkins URL? Could you tell me the file where this is done so I could play around with it and see if I can find a better solution that fits my needs?