Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevTrace breaks AJAX with Vagrant & Custom Domains #318

Open
jamie opened this issue Jan 6, 2020 · 0 comments
Open

DevTrace breaks AJAX with Vagrant & Custom Domains #318

jamie opened this issue Jan 6, 2020 · 0 comments

Comments

@jamie
Copy link
Contributor

jamie commented Jan 6, 2020

When DevTrace is enabled in my local environment, I'm getting broken XHR responses in my app.

Environment: Rails 3 on passenger on nginx, inside Vagrant/VirtualBox. We're using custom subdomains for namespacing, but I'm not actually sure if that's relevant, other than I'm not directly visiting localhost:3000 in development.

Behaviour without dev_trace - XHR request returns a 200 OK with expected response

Behavior with dev_trace: true - XHR request returns a 502 Bad Gateway, but backend rails logs still show successful response.

In both cases, the browser was sending identical requests & headers, and if I copy the request as a curl command, I can reproduce the differing behaviour just by restarting the server in vagrant with SCOUT_DEV_TRACE=true.

I'm not sure what other info will be helpful in tracing this, but do ping me (I can repro trivially, and get whatever you need).

@jamie jamie changed the title DevTrace breaks AJAX with custom domains DevTrace breaks AJAX with Vagrant & Custom Domains Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant