I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
It should be possible to add localhost to the CORS whitelist in settings (I’m pretty sure the entire frontend team is doing exactly that). What are you adding to it? I think you need the full protocol host and port, so something like http://localhost:8081 for example.
Another solution would be to setup a proxy yourself, it kinda depends on your setup… but if you are serving up your app using node, you can use one of the many the proxy libraries available for it.
If you are using something like CRA (create-react-app), it includes a proxy already and you can just map that to your DHIS2 instance.
Please be aware that the live package has some issues with analytics (unless you have mapped it to use a local postgres service), another approach could be to use dhis2-docker [1].
I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
We have an alternative Docker project here as well with pre-built images on Dockhub as well which you also may want to check out.
Regards,
Jason
···
On Tue, Dec 19, 2017 at 6:12 AM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Chase
It should be possible to add localhost to the CORS whitelist in settings (I’m pretty sure the entire frontend team is doing exactly that). What are you adding to it? I think you need the full protocol host and port, so something like http://localhost:8081 for example.
Another solution would be to setup a proxy yourself, it kinda depends on your setup… but if you are serving up your app using node, you can use one of the many the proxy libraries available for it.
If you are using something like CRA (create-react-app), it includes a proxy already and you can just map that to your DHIS2 instance.
Please be aware that the live package has some issues with analytics (unless you have mapped it to use a local postgres service), another approach could be to use dhis2-docker [1].
I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
I’m using the App Skeleton (https://github.com/dhis2/app-skeleton ) to make calls to the API served through DHIS2 Live (with my localhost whitelisted as you showed). I’ve been thinking I need look more into ‘http-proxy’ and configure my proxy correctly and your comments may confirm that suspicion. I won’t really be running analytics as I’m just working on a concept using D2 but I think I’ll switch over to using Docker just for modernity’s sake.
Thanks!
Chase
···
Hi Chase
It should be possible to add localhost to the CORS whitelist in settings (I’m pretty sure the entire frontend team is doing exactly that). What are you adding to it? I think you need the full protocol host and port, so something like http://localhost:8081 for example.
Another solution would be to setup a proxy yourself, it kinda depends on your setup… but if you are serving up your app using node, you can use one of the many the proxy libraries available for it.
If you are using something like CRA (create-react-app), it includes a proxy already and you can just map that to your DHIS2 instance.
Please be aware that the live package has some issues with analytics (unless you have mapped it to use a local postgres service), another approach could be to use dhis2-docker [1].
I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
We have an alternative Docker project
here as well with pre-built images on
Dockhub as well which you also may want to check out.
Regards,
Jason
On Tue, Dec 19, 2017 at 6:12 AM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Chase
It should be possible to add localhost to the CORS whitelist in settings (I’m pretty sure the entire frontend team is doing exactly that). What are you adding to it? I think you need the full protocol host and port, so something like http://localhost:8081 for example.
Another solution would be to setup a proxy yourself, it kinda depends on your setup… but if you are serving up your app using node, you can use one of the many the proxy libraries available for it.
If you are using something like CRA (create-react-app), it includes a proxy already and you can just map that to your DHIS2 instance.
Please be aware that the live package has some issues with analytics (unless you have mapped it to use a local postgres service), another approach could be to use dhis2-docker [1].
I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
Subject: Re: [Dhis2-devs] DHIS2 Live / Jetty v.3 / CORS
Hi Chase,
We have an alternative Docker project
here as well with pre-built images on
Dockhub as well which you also may want to check out.
Regards,
Jason
On Tue, Dec 19, 2017 at 6:12 AM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Chase
It should be possible to add localhost to the CORS whitelist in settings (I’m pretty sure the entire frontend team is doing exactly that). What are you adding to it? I think you need the full protocol host and port, so something like http://localhost:8081 for example.
Another solution would be to setup a proxy yourself, it kinda depends on your setup… but if you are serving up your app using node, you can use one of the many the proxy libraries available for it.
If you are using something like CRA (create-react-app), it includes a proxy already and you can just map that to your DHIS2 instance.
Please be aware that the live package has some issues with analytics (unless you have mapped it to use a local postgres service), another approach could be to use dhis2-docker [1].
I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
I’ve gotten tied up with work on another project. But I will keep you informed when I give it another shot. For now this is just a “pet project” of mine in my spare time.
Though, perhaps Nicolay could try and replicate the issue using DHIS2 Live and the D2 Skeleton-app, since I believe he created it.
Thank you for following up Morten, I’ll be in touch.
Chase
···
Ok, so are you successful or not? Adding in frontend team just in case…
Subject: Re: [Dhis2-devs] DHIS2 Live / Jetty v.3 / CORS
Hi Chase,
We have an alternative Docker project here as well with pre-built images on Dockhub as well which you also may want to check out.
Regards,
Jason
On Tue, Dec 19, 2017 at 6:12 AM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Chase
It should be possible to add localhost to the CORS whitelist in settings (I’m pretty sure the entire frontend team is doing exactly that). What are you adding to it? I think you need the full protocol host and port, so something like
http://localhost:8081 for example.
Another solution would be to setup a proxy yourself, it kinda depends on your setup… but if you are serving up your app using node, you can use one of the many the proxy libraries available for it.
If you are using something like CRA (create-react-app), it includes a proxy already and you can just map that to your DHIS2 instance.
Please be aware that the live package has some issues with analytics (unless you have mapped it to use a local postgres service), another approach could be to use dhis2-docker [1].
I’m getting started with using the D2 library and I had intended to use the DHIS2 Live package to quickly get started in a test environment. I’ve run into some crippling CORS errors and investigated the Jetty Servlet’s web.xml file to see if I could allow for cross-origin requests. Alas, when I tried to insert the filter it would fail time no matter the configuration. Is this because it is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? The CORS whitelist in Access Settings is not working for Localhost.
Any tips/assistance in using DHIS2 Live to work with the D2 Library would be much appreciated.
Adding in frontend team just in case…