Skip to main content
Archived

Support for subdomain wildcards in CORS Allowed Origins (*.domain.com)

Related products:FME Form
siennaatsafe
redgeographics
danilo_fme
caracadrian
warrendev
+21
  • siennaatsafe
    siennaatsafe
  • redgeographics
    redgeographics
  • danilo_fme
    danilo_fme
  • caracadrian
    caracadrian
  • warrendev
    warrendev
  • tcrossman
    tcrossman
  • j.botterill
    j.botterill
  • stalknecht
    stalknecht
  • fgiron
    fgiron
  • mgg_beca
    mgg_beca
  • bjudes
    bjudes
  • taudorf
    taudorf
  • rumle
    rumle
  • vadis
    vadis
  • mapsrus
  • chris_rmw
    chris_rmw
  • geobroetchen
    geobroetchen
  • louisput
  • ecthelion
    ecthelion
  • chau
    chau
  • geoportalcartog
    geoportalcartog
  • tino
    tino
  • denniswilhelm
    denniswilhelm
  • marietta
    marietta
  • marvin
  • conterraclara

fmelizard
Safer

Currently in FME Server 2018.0, the FME Server Application Server follows standard CORS guidelines for Apache Tomcat and only allows * (all) or specific hostnames (http://server.domain.com) to be entered into the Allowed Origins Header for CORS.

This idea has been created to collect feedback and interest for supporting wildcards on the subdomain level – for example, http://*.domain.com.

There are a few resources that indicate this would be possible:
https://stackoverflow.com/questions/14003332/access-control-allow-origin-wildcard-subdomains-ports-and-protocols
https://stackoverflow.com/questions/27147737/cors-filter-allow-all-sub-domains
http://starredmediasoft.com/cors-allow-origin-domain-using-wildcard-operator/

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings