Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upissue after migration web API Core 1.0 to 3.1 #681
Assignees
Labels
Comments
|
So things work if you use Postman, but not your app? Some significant changes to routing have been made since 1.0. It sounds like it may be an issue with the code. Do you have more details or a repro to share? |
|
We're you able to get things working? Can you provide some additional context if not? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
We have developed out application using asp.net core 1.0 for UI and Web Api with Core 1.0, and it was working fine, now we have planed to migrate Web Api to 3.1 and we have not migrated UI application. so now when we call the API from UI application i getting error like , we are not getting header values and even model values are null,
But when we try to call the api 3.1 from postman it working fine and able access the methods.
what can we the issue ?