Timeline for Resolve CORS issue without changing services.yml file
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2018 at 10:53 | vote | accept | CommunityBot | ||
| Oct 23, 2018 at 10:39 | comment | added | Clive♦ |
Yep, you'll need to implement your own middleware service, or find a way to get your required config to the existing http_middleware.cors middleware without using the services from system.yml. You also need to bear in mind that if the cors.config is missing, Drupal will disable that service (in Drupal\Core\DependencyInjection\Compiler\CorsCompilerPass), so you're always going to be fighting against core. Probably best to implement your own middleware and config completely separate from core's
|
|
| Oct 23, 2018 at 10:22 | comment | added | user9589 | I totally agree with you. But due to limitations we can't change in services.yml. So is there any alternatives to achieve it? | |
| Oct 23, 2018 at 9:05 | history | answered | Clive♦ | CC BY-SA 4.0 |