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

Some redirects result in 404s #48

Open
mustberuss opened this issue Sep 6, 2020 · 4 comments
Open

Some redirects result in 404s #48

mustberuss opened this issue Sep 6, 2020 · 4 comments

Comments

@mustberuss
Copy link

Hi,
The redirects sent back from the uspc, cpc and nber endpoints result in 404s. Also posts from web pages like https://mustberuss.github.io/Patentsview-Swagger/ seem to be blocked by CORS after the recent api update.

@sarvothaman
Copy link
Contributor

@mustberuss Thank you for reporting the issue. CORS was temporarily turned off when implementing the redirect. It's been enabled again. The issue with 404 from redirect is also fixed.

Thanks!

@mustberuss
Copy link
Author

@sarvothaman The redirects are working! I'm still not able to post from a web page like this one though: http://patentsview.historicip.com/ricepost.htm

@sarvothaman
Copy link
Contributor

@mustberuss It looks like the Access Control Allow Origin header requires explicit specification of allowed headers. This has been resolved now.

@mustberuss
Copy link
Author

Thanks @sarvothaman, the post works now. Could the same thing be done on an error? If I make a bad request the response is getting blocked and I can't access the X-Status-Reason header. See http://patentsview.historicip.com/bad_req.htm The same thing happens from my swagger page where users may not realize the mistake they made in their request.

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