unable to execute requests after Friday's update - 404 Not Found #8775
Assignees
Labels
Comments
|
Can you share more details about the request or a scaled-down collection/endpoint which we can use to reproduce this issue? |
|
Hello Udit,
I am sending you the request and POST URL . but its in out QA environment. Not sure how you will be execute the same.
URL : https://qa-edfi-api.tneducation.net/api/v31/ed-fi/classPeriods
{
"classPeriodName": "02 - Traditional",
"schoolReference": {
"schoolId": 47
},
"_ext": {
"tdoe": {
"submittedForSchoolYearTypeReference": {
"schoolYear": 2020
},
"submittedByEducationOrganizationReference": {
"educationOrganizationId": 47
}
}
}
}
[Small Department Logo for Email Signature]
Minakshi Goel| QA
Andrew Johnson Bldg, 10th Floor
710 James Robertson Pkwy, Nashville, TN 37243
615-770-3873
tn.gov/education
#TNBestforAll
From: Udit Vasu <notifications@github.com>
Sent: Tuesday, July 14, 2020 9:05 AM
To: postmanlabs/postman-app-support <postman-app-support@noreply.github.com>
Cc: Minakshi Goel <Minakshi.Goel@tn.gov>; Author <author@noreply.github.com>
Subject: [EXTERNAL] Re: [postmanlabs/postman-app-support] unable to execute requests after Friday's update - 404 Not Found (#8775)
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email - STS-Security. ***
…________________________________
Can you share more details about the request or a scaled-down collection/endpoint which we can use to reproduce this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8775*issuecomment-658199650__;Iw!!PRtDf9A!6Zgt0cBm-WXsEOEB49X8CwnRZ_W1gFr6y9r8_1iLvnhEVDDbWk1XHksi7_9fCwew8mA$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBTKA5CE4IL53EJJJLNKZ3R3RQX7ANCNFSM4OZRPVWA__;!!PRtDf9A!6Zgt0cBm-WXsEOEB49X8CwnRZ_W1gFr6y9r8_1iLvnhEVDDbWk1XHksi7_9fTmQzTro$>.
|
|
This internal API will not help but due to 404, this problem looks specific to this particular endpoint. Are you getting 404s for all the |
|
I am also getting this issue but with a GET request that is using pipelines in the query string. |
|
I got the same error on one of our GET request yesterday.
Something is definitely wrong. All the end points were working until Friday.
Appreciate your quick help.
Thanks
Minakshi
From: Alan Parsons <notifications@github.com>
Sent: Wednesday, July 15, 2020 6:49 AM
To: postmanlabs/postman-app-support <postman-app-support@noreply.github.com>
Cc: Minakshi Goel <Minakshi.Goel@tn.gov>; Author <author@noreply.github.com>
Subject: [EXTERNAL] Re: [postmanlabs/postman-app-support] unable to execute requests after Friday's update - 404 Not Found (#8775)
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email - STS-Security. ***
…________________________________
I am also getting this issue but with a GET request that is using pipelines in the query string.
For example: list-of-values?q=type=ISAUTO|keyGroup=branch
Returns a 404: The request cannot be fulfilled due to bad syntax.
This is in version 7.28.0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8775*issuecomment-658721884__;Iw!!PRtDf9A!8vcgxTqNnpY9R-z2G_9QIPjlngJac7Rwq_BhFfhheP13qZjeskex51QLu1fQ428LQQI$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBTKA4VM466HNFNWTHBZULR3WJSHANCNFSM4OZRPVWA__;!!PRtDf9A!8vcgxTqNnpY9R-z2G_9QIPjlngJac7Rwq_BhFfhheP13qZjeskex51QLu1fQjaejJ0Y$>.
|
|
@ParsonsProjects In the latest release, the default URL processor is updated due to which you are facing this issue. The As a workaround, you can either manually encode the pm.request.url.query.each((q) => {
q.update(encodeURI(q.toString()))
});You can know more about this change here. |
|
Hello Udit,
So how soon you expect the updated version with this fix?
I practically can not write Pre-request script in all of my 1000s of scripts unless there is some common place to write once and accessed by all. Would be able to help with the same in the meantime?
Thanks
Minakshi
From: Udit Vasu <notifications@github.com>
Sent: Wednesday, July 15, 2020 9:56 PM
To: postmanlabs/postman-app-support <postman-app-support@noreply.github.com>
Cc: Minakshi Goel <Minakshi.Goel@tn.gov>; Author <author@noreply.github.com>
Subject: [EXTERNAL] Re: [postmanlabs/postman-app-support] unable to execute requests after Friday's update - 404 Not Found (#8775)
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email - STS-Security. ***
…________________________________
@ParsonsProjects<https://urldefense.com/v3/__https:/github.com/ParsonsProjects__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfJ-TAPbU$> In the latest release, the default URL processor is updated<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8154__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMf_qYYbXg$> due to which you are facing this issue.
The | used in the query string are no longer encoded by default which is causing the issue at your server-side.
This is because | is not an unsafe character in the query and hence doesn't require encoding. You might be facing the same issue when you send this request from any browser.
As a workaround, you can either manually encode the | to %7C or add the following script as part of your Pre-request script:
pm.request.url.query.each((q) => {
q.update(encodeURI(q.toString()))
});
You can know more about this change here<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8154__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMf_qYYbXg$>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8775*issuecomment-659126717__;Iw!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfMO_AzIg$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBTKA2PJLFRXJ2QWAFKYTTR3ZT3LANCNFSM4OZRPVWA__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfGD_LuKM$>.
|
|
Hello Udit,
Unfortunately, the Pre-request script did not work. Still getting 404 Not Found !
Thanks,
Minakshi
From: Udit Vasu <notifications@github.com>
Sent: Wednesday, July 15, 2020 9:56 PM
To: postmanlabs/postman-app-support <postman-app-support@noreply.github.com>
Cc: Minakshi Goel <Minakshi.Goel@tn.gov>; Author <author@noreply.github.com>
Subject: [EXTERNAL] Re: [postmanlabs/postman-app-support] unable to execute requests after Friday's update - 404 Not Found (#8775)
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email - STS-Security. ***
…________________________________
@ParsonsProjects<https://urldefense.com/v3/__https:/github.com/ParsonsProjects__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfJ-TAPbU$> In the latest release, the default URL processor is updated<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8154__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMf_qYYbXg$> due to which you are facing this issue.
The | used in the query string are no longer encoded by default which is causing the issue at your server-side.
This is because | is not an unsafe character in the query and hence doesn't require encoding. You might be facing the same issue when you send this request from any browser.
As a workaround, you can either manually encode the | to %7C or add the following script as part of your Pre-request script:
pm.request.url.query.each((q) => {
q.update(encodeURI(q.toString()))
});
You can know more about this change here<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8154__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMf_qYYbXg$>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8775*issuecomment-659126717__;Iw!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfMO_AzIg$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBTKA2PJLFRXJ2QWAFKYTTR3ZT3LANCNFSM4OZRPVWA__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfGD_LuKM$>.
|
|
Is there any way to revert the update and go back to previous version without disturbing anything else?
Thanks
Minakshi
From: Udit Vasu <notifications@github.com>
Sent: Wednesday, July 15, 2020 9:56 PM
To: postmanlabs/postman-app-support <postman-app-support@noreply.github.com>
Cc: Minakshi Goel <Minakshi.Goel@tn.gov>; Author <author@noreply.github.com>
Subject: [EXTERNAL] Re: [postmanlabs/postman-app-support] unable to execute requests after Friday's update - 404 Not Found (#8775)
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email - STS-Security. ***
…________________________________
@ParsonsProjects<https://urldefense.com/v3/__https:/github.com/ParsonsProjects__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfJ-TAPbU$> In the latest release, the default URL processor is updated<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8154__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMf_qYYbXg$> due to which you are facing this issue.
The | used in the query string are no longer encoded by default which is causing the issue at your server-side.
This is because | is not an unsafe character in the query and hence doesn't require encoding. You might be facing the same issue when you send this request from any browser.
As a workaround, you can either manually encode the | to %7C or add the following script as part of your Pre-request script:
pm.request.url.query.each((q) => {
q.update(encodeURI(q.toString()))
});
You can know more about this change here<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8154__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMf_qYYbXg$>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8775*issuecomment-659126717__;Iw!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfMO_AzIg$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBTKA2PJLFRXJ2QWAFKYTTR3ZT3LANCNFSM4OZRPVWA__;!!PRtDf9A!8WNmQnQs-S23mMx6MUG0ULFBwX0uqGm61HxJtipjH_bmgXouYf4JTTYo_KMfGD_LuKM$>.
|
|
Hey @minakshi-goel! Here's a link to the previous build that should work – https://dl.pstmn.io/download/7.27.1/win64 Does toggling the next-gen URL processing setting off in the latest build yield different results? |
|
Hello Chris,
Toggling worked for couple of POST but GET is still an issue.
Any special instructions to install previous build? Would it overwrite all build files and keep my collections and setup as it is?
Thanks
Minakshi
From: Chris de Sousa <notifications@github.com>
Sent: Thursday, July 16, 2020 12:03 PM
To: postmanlabs/postman-app-support <postman-app-support@noreply.github.com>
Cc: Minakshi Goel <Minakshi.Goel@tn.gov>; Mention <mention@noreply.github.com>
Subject: [EXTERNAL] Re: [postmanlabs/postman-app-support] unable to execute requests after Friday's update - 404 Not Found (#8775)
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email - STS-Security. ***
…________________________________
Hey @minakshi-goel<https://urldefense.com/v3/__https:/github.com/minakshi-goel__;!!PRtDf9A!-twOQma3w_igWeXZiNH6JESp3wgGhGERQWYJjD7M7pTRIXZ1eGIchGOLFhRjIb5ATMU$>!
Here's a link to the previous build that should work – https://dl.pstmn.io/download/7.27.1/win64<https://urldefense.com/v3/__https:/dl.pstmn.io/download/7.27.1/win64__;!!PRtDf9A!-twOQma3w_igWeXZiNH6JESp3wgGhGERQWYJjD7M7pTRIXZ1eGIchGOLFhRjI2TNOFw$>
Does toggling the next-gen URL processing setting off in the latest build yield different results?
<https://urldefense.com/v3/__https:/user-images.githubusercontent.com/4734306/87700636-41053380-c75c-11ea-8111-cd6df4daa05c.png__;!!PRtDf9A!-twOQma3w_igWeXZiNH6JESp3wgGhGERQWYJjD7M7pTRIXZ1eGIchGOLFhRjJI56lr4$>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/postmanlabs/postman-app-support/issues/8775*issuecomment-659544530__;Iw!!PRtDf9A!-twOQma3w_igWeXZiNH6JESp3wgGhGERQWYJjD7M7pTRIXZ1eGIchGOLFhRjnxHsXrs$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBTKA6JO5N3YLJWTAGRZ5DR34XEZANCNFSM4OZRPVWA__;!!PRtDf9A!-twOQma3w_igWeXZiNH6JESp3wgGhGERQWYJjD7M7pTRIXZ1eGIchGOLFhRj51HlOgg$>.
|
This is not an issue, the requests are failing because of the restrictions on the requesting server. You can check the workarounds mentioned here for explicitly encoding additional characters.
Looks like a separate issue then.
Make sure you are logged in and all your unsaved requests are synced. @minakshi-goel To move forward we need more information about the requests or steps which we can follow to reproduce the issue locally. |
|
I also encountered this error, but closing it solved the problem
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am getting "404 Not Found" error for every single request I am executing after Friday's update. All the requests were good before update. This has stopped out testing completely. Could you please look into the issue at your earliest? I am available to talk/web call and show screen
Same requests with same URLs are good if executed thru swagger
This is the version I have :
Postman for Windows
Version 7.28.0
win32 10.0.19041 / x64
The text was updated successfully, but these errors were encountered: