Skip to content

Support SSL connections #391

Closed
holu opened this Issue Feb 21, 2012 · 9 comments

5 participants

@holu
BaseX member
holu commented Feb 21, 2012

Requested by Johannes.H*****

@snivas
snivas commented Apr 13, 2012

Hi,
This is Seenivasan and I am interested in implementing this feature of supporting SSL connections. Could anyone guide from where to start?

As far as, I gone through the code, is it ok if we add extra connecter for SSL in the BaseXHTTP.java ?

Thanks

@ChristianGruen
BaseX member

Seenivasan, thanks a lot for your interest! The BaseXHTTP is a good point to start from, and you'll probably have to modify the web.xml class to also make SSL available if BaseX is started as web application. – We’re looking forward to your contribution!

@ChristianGruen
BaseX member

Dear Seenivasan, did you already have some time to take a closer look at the SSL support?

@snivas
snivas commented May 19, 2012

Dear Christian,
Sorry, I was assigned in to another work for now.

Thanks

@dirkk
BaseX member
dirkk commented Jul 4, 2012

I just send two pull requests (https://github.com/BaseXdb/basex-api/pull/61 and #530), which should add the requested functionality. Changes and help can be found (in a minute...) at http://docs.basex.org/wiki/Startup_Options#BaseX_HTTP_Server

@dirkk
BaseX member
dirkk commented Jul 6, 2012

The solution in my last comment was disregarded in favor of a more flexible approach now using jetty.xml file. The pull request https://github.com/BaseXdb/basex-api/pull/62#issuecomment-6801543 adds the support for jetty.xml and also uses as standard a new SSL connector and thereby fixing this issue.

@dirkk dirkk was assigned Jul 7, 2012
@ChristianGruen
BaseX member

Resolved by switching to jetty.xml config file. Feedback is welcome.

@ChristianGruen
BaseX member

Still needs to be documented.

@arolle arolle was assigned Dec 7, 2012
@ChristianGruen
BaseX member

About to be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.