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

Pagination broken - Next URL more than 2Kb #2250

Closed
shahedaAnsari opened this issue Oct 1, 2021 · 5 comments
Closed

Pagination broken - Next URL more than 2Kb #2250

shahedaAnsari opened this issue Oct 1, 2021 · 5 comments
Labels
Bug Bug bug bug. VSTS-Current We are working on this item in the current sprint
Milestone

Comments

@shahedaAnsari
Copy link

Describe the bug
The "next" url in the link section of a Bundle resource results in a 404 response. I believe this is related to the URL specified as "next" and its length is greater than 4kb.
We are using the Azure API for FHIR.

FHIR Version?
R4

Data provider?
CosmosDB

To Reproduce
Steps to reproduce the behavior:

  1. This occurs when we get all resource example- suppose we get list of patient then in next link we get very long string for parameter "ct"

Expected behavior
Able to navigate to other pages using next link

Actual behavior
Not able to navigate to next link we get following error

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Screenshot for the same

CosmosDBNextLinkTooLong

@shahedaAnsari shahedaAnsari added the Bug Bug bug bug. label Oct 1, 2021
@CaitlinV39
Copy link
Contributor

@shahedaAnsari A couple quick questions. Are you using a proxy in front of the FHIR service or hitting it directly? In addition, are you on the open-source version of the FHIr service or using the Azure API for FHIR? If the open-source version, can you tell me which release you are running?

@shahedaAnsari
Copy link
Author

@shahedaAnsari A couple quick questions. Are you using a proxy in front of the FHIR service or hitting it directly? In addition, are you on the open-source version of the FHIr service or using the Azure API for FHIR? If the open-source version, can you tell me which release you are running?

I am directly hitting the API, and I am using the open source which has the version 2.0.172

@CaitlinV39 CaitlinV39 added the Review Tag for PM/Dev Review label Oct 13, 2021
@CaitlinV39 CaitlinV39 added VSTS-Pending Prioritization We would like to add this to the backlog and removed Review Tag for PM/Dev Review labels Oct 15, 2021
@CaitlinV39
Copy link
Contributor

CaitlinV39 commented Oct 15, 2021

AB#86024

@CaitlinV39 CaitlinV39 added VSTS-Current We are working on this item in the current sprint and removed VSTS-Pending Prioritization We would like to add this to the backlog labels Oct 15, 2021
@CaitlinV39 CaitlinV39 added this to the S73 milestone Oct 15, 2021
@CaitlinV39
Copy link
Contributor

@shahedaAnsari - We have merged a fix for this into main. Please let us know if you are still having any issues.

@Sameer2810
Copy link

Still facing same issue with new build 2.1.22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug bug bug. VSTS-Current We are working on this item in the current sprint
Projects
None yet
Development

No branches or pull requests

3 participants