amazon-price

부분 유료
분류별 Dhananjoy Biswas | 업데이트됨 4달 전 | eCommerce
인기

8.7 / 10

지연 시간

3,092ms

서비스 수준

100%

모든 토론으로 돌아가기

API keep returning Parse Error

avatar
itjesse54
3년 전

API keep returning Parse Error

avatar
ebappa1971 commented 2년 전

It’s fixed now! If you’re still facing this, just unsubscribe and then resubscribe again.

(Details: there was a problem with header names in RapidAPI platform, I’ve updated the header names but old account still might use problematic header names. Resubscribing will solve this problem)

G
gtsystems commented 2년 전

i receive Parse Error every time. Do I get charged for these Error Calls?

avatar
itjesse54 commented 3년 전

Maybe there is something wrong with RapidAPI server.

avatar
itjesse54 commented 3년 전
avatar
itjesse54 commented 3년 전

It seems like a TLS error.

$ node test.js
/xxx/test.js:14
if (error) throw new Error(error);
^

Error: Error: Parse Error: Invalid header token
at Request._callback (/xxx/test.js:14:20)
at self.callback (/xxx/node_modules/request/request.js:185:22)
at Request.emit (events.js:305:20)
at Request.onRequestError (/xxx/node_modules/request/request.js:881:8)
at ClientRequest.emit (events.js:305:20)
at TLSSocket.socketOnData (_http_client.js:477:9)
at TLSSocket.emit (events.js:305:20)
at addChunk (_stream_readable.js:341:12)
at readableAddChunk (_stream_readable.js:316:11)
at TLSSocket.Readable.push (_stream_readable.js:250:10)

avatar
ebappa1971 commented 3년 전

Hello!
Are you facing Parse Error when testing with code or only in the website? There seems to be a glitch with rapidapi platform that’s causing it to show Parse Error in the website.

아래에 의견을 추가하고 토론에 참여하세요.

새 댓글을 게시하려면 로그인 / 가입
등급: 5 - 투표: 1