How to download the Orthanc source code the official source code which is present on mercurial.? and what are the tools required to open that orthanc source code for development purpose like (Visual Studio or VS Code etc.)
Hello,
The source code of the official releases can be downloaded from the homepage:
https://www.orthanc-server.com/browse.php?path=/orthanc
Here are the instructions to use Mercurial:
https://book.orthanc-server.com/developers/repositories.html
https://hg.orthanc-server.com/
The developers of the Orthanc core use different IDE, including Microsoft Visual Studio, Qt Creator and VS Code. As far as I’m concerned, I use emacs (and cgdb for debugging).
You can find information about how to compile Orthanc in the Orthanc Book:
https://book.orthanc-server.com/faq/compiling.html
Sébastien-
Can you please tell me what are web servers on which I can deploy Orthanc?
Well, Orthanc IS a webserver itself. What do you mean exactly ?
means can I be able to deploy Orthanc on servers like IIS, Apache, etc.???
Secondly, if Orthanc is a webserver itself then from where we can be able to set its cores.
Thanks
Please read the FAQ for info on how to run Orthanc behind Apache/IIS/nginx: https://book.orthanc-server.com/faq.html
Don’t understand what you mean by “set its cores” … you can not configure the number of cores Orthanc runs on if this is what you mean. Orthanc uses all available cores.
Sorry, I am talking about CORS, not cores.
Can we set CORS in the Orthanc webserver code?
CORS is not supported by the built-in Web server of Orthanc. The Orthanc Book contains instructions to enable CORS by using nginx as a reverse proxy to Orthanc:
https://book.orthanc-server.com/faq/nginx.html#enabling-cors
I have applied the reverse proxy using the Nginx server as well as the IIS server. now the problem is that I am getting the list of studies from the Orthanc server in OHIF viewer which is fine but clicking on any study, it should show me series, but again I am getting an error related to the CORS issue. even I have applied the IIS reverse proxy. See the below images.
Thanks
Your origin is http://localhost:3000 while orthanc is at http://localhost/orthanc (which means on port 80) → that’s 2 different servers.
You probably still have a http://localhost/orthanc hardcoded address somewhere while you should use a relative address ‘/orthanc’ which would translate into http://localhost:3000/orthanc.
yeah, here in the default.js Configuration File I have these details.
and also as I told you earlier that I am using reverse proxy and running my Orthanc PACS server behind IIS on Port 80. so that’s why I hardcoded this address in the default.js file.
And as I told you earlier: You DO HAVE a http://localhost/orthanc hardcoded address while you SHOULD PROBABLY USE a relative address ‘/orthanc’ which would translate into http://localhost:3000/orthanc.
Do you mean I have to use this relative address ‘/orthanc’ in the default.js file instead of writing this (http://localhost/orthanc/dicom-web) full address?
i have the same problem as @farooqahmed,in default.js i put http://@myOrthancIP/orthanc/dicom-web but the CORS error still appears CORS error:Cross-Origin Resource Sharing error MissingAllowOrihinHeader
PS:i am trying to integrate Orthanc server in the OHIF viewer
But why don’t you try with the relative address like I’ve been suggesting ?
If this default.js is a configuration for the OHIF frontend, that should solve your CORS issues. BTW, this users group is not the OHIF support so you’ll get better information at OHIF. On my side, I can’t help any further.
in my humble opinion i think that the CORS error comming from Orthanc server and OHIF support suggested that to configure cors in orthanc with nginx. .Please correct me if I am wrong,but default.js configuration to give orthanc connexion settings
dicomWeb: [
{
name: ‘Orthanc’,
wadoUriRoot: ‘http:// x.1.200.7 :8042/wado’,
qidoRoot: ‘http://x.1.200.7:8042’,
wadoRoot: ‘http://x.1.200.7:8042’,
qidoSupportsIncludeField: false,
imageRendering: ‘wadors’,
thumbnailRendering: ‘wadors’,
enableStudyLazyLoad: true,
},
Hello,
As written in the Orthanc Book: “The OHIF viewer can connect to Orthanc using the DICOMweb plugin of Orthanc, but is a fully separate project. As a consequence, questions regarding OHIF must be asked on the dedicated discussion group or on the dedicated bug tracker. The core developers of Orthanc will happily fix the DICOMweb plugin, but it is necessary for the reporter to identify the discrepancy wrt. DICOMweb standard by providing a minimal working example as explained above.”
https://book.orthanc-server.com/users/support.html#discussing-a-minimal-working-example
Sébastien-