Hi all Sorry for late reply. That's not a good solution for production environment anyway.
My guess is that both DSpace and angular should work in local IP addresses and local ports and only Apache/nginx should be exposed and therefore proxy requests per location/request to corresponding endpoint. So Apache's conf should look something like this #DSpace backend ProxyPass /server http://127.0.0.1:8080/server ProxyPassReverse /server http://127.0.0.1:8080/server # angular UI ProxyPass / http://127.0.0.1:4000/ ProxyPassReverse / http://127.0.0.1:4000/ (Or you can use your internal network IP addresses as well, you don't have to use 127.0.0.1) The thing is that this causes mixed response and request is blocked. Also, when accessing backend via URL, server URL is replaced with 127.0.0.1, but not with actual domain, like it's in the Atmire's demo page. On Friday, February 26, 2021 at 7:35:52 PM UTC+2 Michael Plate wrote: > Am 26.02.21 um 18:30 schrieb Sten Aus: > > Is there someone from Atmire team here to possibly see my request or am > > I alone in the dark? :D > […] > > well, I got it running partially behind a simple Apache reverse proxy - > means, I had CORS errors in FF. > > It however worked with Chrome (google-chrome-stable > --disable-web-security --disable-gpu --user-data-dir=/tmp) and I was > able to login (in prod mode, dev does not work because of websockets). > > Michael > > > -- All messages to this mailing list should adhere to the 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/6c0387f7-1a40-4a66-91f9-b858fe9b32c2n%40googlegroups.com.
