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

"Error loading feed" in elm with .NET backend #68

Open
clearhat opened this issue Jan 16, 2019 · 1 comment
Open

"Error loading feed" in elm with .NET backend #68

clearhat opened this issue Jan 16, 2019 · 1 comment

Comments

@clearhat
Copy link

clearhat commented Jan 16, 2019

Documentation is kinda sparse on this point, so I found out that I needed to change the url in Endpoint.elm by opening up Fiddler and watching traffic to see where my site was loading from. I found the following URL in that file, and changed it (to "http://localhost:5000"):

Url.Builder.crossOrigin "https://conduit.productionready.io"

That allowed me to talk to my backend instead of the default demo, or so I thought. But when the first page loads, I get: Error loading feed. Error loading tags.

On the backend side, I'm getting a vague error, which a Google search says is just telling me that the inbound URL (being sent by elm) is malformed. But at least I know I'm talking to the backend server:

"Microsoft.AspNetCore.Server.Kestrel Connection id '0HLJS3KI1AV8A', Request id '0HLJS3KI1AV8A:00000004': the application completed without reading the entire request body."

I downloaded the React/Redux frontend and got that working, so I know the backend is performing properly once I hit it, but it's not working in ELM version for some reason.

@nikolisgal
Copy link

Do you have the same rest calls in your back end as https://conduit.productionready.io has ?
Because it looks like you are calling your back end using url paths and parameters intended to query https://conduit.productionready.io for feed which are the article outlines. If you post a bit more information on what you have done or trying to achieve I might be able to help a bit because I actually ported this front end to use my elixir phoenix back end without a problem.

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

2 participants