#497 CORS not always enabled

Reporter emmanuel.florent
Owner MattJ
Created
Updated
Stars ★ (1)  
Tags
  • Priority-Medium
  • Status-CantReproduce
  • Type-Defect
  1. emmanuel.florent on

    *What steps will reproduce the problem?* 1. Install conversejs 2. Prosody 0.9 with cross_domain_bosh = true 3. Set up auto_login and login an unregistred user What is the expected output? Expected output should be user rejected Instead No 'Access-Control-Allow-Origin' header Ubuntu Trusty Prosody 0.9 official package both in a Docker container In my setup I can login a registered user and register a new user using Prosody's Bosh module, Prosody's CORS implementation, Prosody 0.9 I had the same result with prosody 0.9 .deb package from trunk using repository found on the official site.

  2. emmanuel.florent on

    I fixed my work disabling prosody's CORS and add CORS Headers via Nginx

  3. MattJ on

    Hi, thanks for the report. Can't reproduce this. Where in the config did you set the option?

    Changes
    • owner MattJ
  4. Zash on

    Setting needinfo to make issues with unanswered questions easier to find later.

    Changes
    • tags Status-NeedInfo
  5. Zash on

    Closing due to no response for almost 2 years.

    Changes
    • tags Status-CantReproduce

New comment