Hi all, How about I describe what I *think* happens, and you can tell me where I'm wrong, where I'm right (if anywhere!) and anything I'm missing?
A user issues a request in a browser for something like https://hdl.handle.net/2123/21886 , which sends a HTTP request to hdl.handle.net. At CNRI, the handle.net proxies or root handle service resolve the handle prefix to a homed handle server and forward the request (UDP on port 2641?) on to it. In this case, this is our standalone handle server homed to 2123. The Remote-Handle-Resolver plugin in turn forwards the request on to the DSpace server (and my knowledge is muddy here) where the handle server on the DSpace server (by some process unknown to me) resolves the handle to a URL from the database. The DSpace server then issues this HTTP response back to the requesting client with a DSpace URL. Is that close? Thanks a lot, Gary On Monday, February 3, 2020 at 8:53:45 AM UTC+11, Gary Browne wrote: > > Hi all, > > I'm not after a "how to" here, rather a conceptual/technical description > of how a set up with CNRI handle.net, a standalone handle server with the > https://github.com/DSpace/Remote-Handle-Resolver plugin, and DSpace (with > its in-built handle server) works together to resolve handles to a DSpace > URL. > > If anyone can shed some light, it would be very much appreciated. > > Thanks, > Gary > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/6462318b-0ef2-49e7-bc22-4d53797bea68%40googlegroups.com.
