Started by an SCM change66be45a6e1ddcb44731760c1393c195348f2261840be45a6e1ddcb44731760c1393c195348f2261840origin/developbe45a6e1ddcb44731760c1393c195348f2261840be45a6e1ddcb44731760c1393c195348f2261840origin/developbe45a6e1ddcb44731760c1393c195348f2261840be45a6e1ddcb44731760c1393c195348f2261840origin/develophttp://sing-group.org/dt/gitlab/dgss-2324-teamA/microstories.gitfalse#66132851194095microstories-2324-teamA #6666false6673SUCCESS1701185470112http://sing.ei.uvigo.es/dt/jenkins/view/all/job/microstories-2324-teamA/66/web/src/main/angular/src/environments/environment.tsCONTRIBUTING.mdweb/src/main/angular/package.jsonweb/src/main/angular/src/environments/environment.development.tsweb/src/main/angular/package-lock.jsonweb/src/main/angular/angular.jsonbe45a6e1ddcb44731760c1393c195348f22618401701185349000http://sing.ei.uvigo.es/dt/jenkins/user/mrjatoMiguel Reboiro-Jatomrjato@uvigo.esFixes communication between frontend and backend On the one hand, the frontend was always using the pre-production backend. On the other hand, the pre-production frontend is being served over HTTPS, but the backend URL was using the HTTP protocol, so there was a security error. This commit fixes these problems, with the cost that now during development it is necessary to use Angular's own server for the frontend (although this was already the recommended option). 2023-11-28 16:29:09 +0100be45a6e1ddcb44731760c1393c195348f2261840Fixes communication between frontend and backendaddweb/src/main/angular/src/environments/environment.development.tseditweb/src/main/angular/src/environments/environment.tseditCONTRIBUTING.mdeditweb/src/main/angular/package-lock.jsoneditweb/src/main/angular/package.jsoneditweb/src/main/angular/angular.jsongithttp://sing.ei.uvigo.es/dt/jenkins/user/mrjatoMiguel Reboiro-Jato3.6.3