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

An ajp - connector would be really helpful for system integration #355

Closed
gitblit opened this issue Aug 12, 2015 · 9 comments
Closed

An ajp - connector would be really helpful for system integration #355

gitblit opened this issue Aug 12, 2015 · 9 comments

Comments

@gitblit
Copy link
Owner

gitblit commented Aug 12, 2015

Originally reported on Google Code with ID 59

What version of the product are you using? On what operating system?

Gitblit GO ( 0.8.2 )

---
It would be awesome to have a ajp connector to integrate the Gitblit GO into a http-server.


This would be consistent to other java app servers and things like e.g. standalone
jenkins/hudson (which includes the winstone servlet container).

As Gitblit GO is using jetty, it should be possible to expose its ajp-interface.

Reported by kosta.grails on 2012-02-07 16:30:05

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

An additional (32KB) jar is needed for this feature 
'org.eclipse.jetty:jetty-ajp:7.4.3.v20110701'

Reported by kosta.grails on 2012-02-07 16:47:39

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Reported by James.Moger on 2012-02-07 18:04:10

  • Status changed: Accepted
  • Labels added: Milestone-0.9.0

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

I forgot to mention that this feature request implicates a second ability. 

You need to be able to set the context of the application. 
Instead of https://hostname:8443/ you need to be able,
to set the context to something like https://hostname:8443/appcontext (etc. https://hostname:8443/gitblit/).

Maybe that was obvious, but I just wanted to mention it for the sake of completeness.

Reported by kosta.grails on 2012-02-08 13:26:15

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

I've never used AJP before so to me it was not obvious.  :)  Having said that a few
months ago someone needed to map the context path for mod_proxy. So server.contextPath
was added.

Reported by James.Moger on 2012-02-08 13:38:57

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

This is implemented on master.

Now that I have done it, I'm wondering how useful it really is since mod_proxy with
http seems to accomplish the same thing and the configuration is nearly identical.

Reported by James.Moger on 2012-02-09 22:16:41

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Reported by James.Moger on 2012-02-09 22:50:44

  • Status changed: Queued

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Well as far as I know you can use mod_proxy module with all sort of interfaces like
http, ajp etc. etc.
But e.g. for load-balancing you would need use the ajp-interface. Load-balancing is
obviously not necessary for gitblit. I don't see why someone would try to scale gitblit
;)

As far as I understood the ajp interface is usually the better fitting connector for
java applications. It can be used with mod_jk (which I mostly use exclusive for such
tasks) and it is an easy way to expose an app in the http-server without the app opening
its own http(s) ports.

I guess you could bind the http(s) interface to localhost only and achieve similar
effects.

Still I'm not the expert on the topic, basically I just got used that in general Java-Apps
provide ajp-connectors. 

Reported by kosta.grails on 2012-02-10 14:38:06

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Fixed in v0.9.1

Reported by James.Moger on 2012-03-28 00:02:10

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Fixed in v0.9.1. Closing.

Reported by James.Moger on 2012-03-28 00:03:13

  • Status changed: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants