Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11278

Can't set source code browser in the project config (http 403)

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • jenkins 1.430 - tomcat 6 - java 1.6.0_25

      When trying set sventon 2.x as a source browser for subversion on a project I get a http 403 error.
      Apparently jenkins uses the proxy definition from plugin management/Advanced tab of the general configuration.
      I think it should work with sventon deployed inside a lan even if we download the plugins from the web.

          [JENKINS-11278] Can't set source code browser in the project config (http 403)

          The proxy setting is considered a part of the system-wide setting, not just for update center, despite where it shows up in the UI. And as you can imagine, if we change this not to use the proxy, we'll hear from others in the opposite direction — someone who runs Jenkins inside a firewall that checks out and uses a repository on the internet.

          A sensible web proxy should support local intranet lookup. I encourage you to talk to your proxy administrators to do this. This will avoid hard problems for all those HTTP clients when they fail to have "non proxy host" configured.

          I think the proper fix to this problem is to expand the proxy configuration to support "no proxy host."

          Kohsuke Kawaguchi added a comment - The proxy setting is considered a part of the system-wide setting, not just for update center, despite where it shows up in the UI. And as you can imagine, if we change this not to use the proxy, we'll hear from others in the opposite direction — someone who runs Jenkins inside a firewall that checks out and uses a repository on the internet. A sensible web proxy should support local intranet lookup. I encourage you to talk to your proxy administrators to do this. This will avoid hard problems for all those HTTP clients when they fail to have "non proxy host" configured. I think the proper fix to this problem is to expand the proxy configuration to support "no proxy host."

          François Houdebert added a comment - - edited

          Thanks for your reply, I was surprised because I can checkout source from svn on port 80 without trouble but not on port 8080 to browse from sventon.
          I will wait for the "no proxy host" configuration improvement. Meanwhile I will activate proxy during update only.

          François Houdebert added a comment - - edited Thanks for your reply, I was surprised because I can checkout source from svn on port 80 without trouble but not on port 8080 to browse from sventon. I will wait for the "no proxy host" configuration improvement. Meanwhile I will activate proxy during update only.

          evernat added a comment - - edited

          duplicate of JENKINS-8710:
          "no proxy hosts" is now supported in the proxy configuration, since Jenkins 1.443

          evernat added a comment - - edited duplicate of JENKINS-8710 : "no proxy hosts" is now supported in the proxy configuration, since Jenkins 1.443

            Unassigned Unassigned
            fhoudebert François Houdebert
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: