SOAP -> REST needs much more Time

Hello,

Have a good new year....

All functions now switched from SOAP to REST

but

POST-Types (PUT is not testet by now, but i think it is the same) for feedback and item have a Time (timeout) Problem, all POSTs need 60 seconds before the OK Response comes back. Failure response comes promptly. So it is not usable. Please do not switch off the SOAP System before this problem is fixed/cleared. This functions we have not switched yet.

best wishes

Hello klaus_schneider,

I have tested from several sources, I don't encounter slowness in sending POST requests. Which library do you use? Can you try to send request with an API client as Postman tocheck that the problem is ours?

Best wishes,
--
Thomas
Delcampe Team

Hello,
can you give me an email address, so i can send you detailed technical informations. write to
ks@briefmarken-schneider.de
best wishes

Hello Klaus,

You can share the technical details here to benefit other users as well. Just take care to hide your confidential information.

Best Regards,
--
Thomas
Delcampe Team

Your request was taken into account!

OK, i cannot post the infos in this window, there are no longer visible after sending.

Nest Try, but i am not shure the info is compleed with this sign translation...

We are having issues with the REST-API as currently provided.
There are 2 situations.

1.
If we send a standard complying request (see the following dump), we get a status 200 XML response, only.
That's fine, but we are running somehow in a time-out, because the server needs 60 seconds to respond.

07. 01. 2021 16:19:20 Senging . . . .
Buffer:000001E6A6A9159C Position:000001FE AllocSize:640 UsedSize:510
00000000 50 4F 53 54 20 2F 69 74 65 6D 2F 31 31 33 33 32 37 30 34 36 POST. / item/ 113327046
00000014 34 2F 62 75 79 65 72 2F 72 61 74 69 6E 67 3F 74 6F 6B 65 6E 4/ buyer/ rating?token
00000028 3D 38 65 61 62 61 33 39 30 62 65 65 62 62 35 34 66 33 30 66 =8eaba390beebb54f30f
0000003C 64 35 63 37 61 30 33 32 61 62 34 30 32 20 48 54 54 50 2F 31 d5c7a032ab402. HTTP/ 1
00000050 2E 31 0D 0A 48 6F 73 74 3A 20 72 65 73 74 2E 64 65 6C 63 61 . 1. . Host:. rest. delca
00000064 6D 70 65 2E 6E 65 74 0D 0A 41 63 63 65 70 74 3A 20 61 70 70 mpe. net. . Accept:. app
00000078 6C 69 63 61 74 69 6F 6E 2F 78 6D 6C 3B 76 65 72 73 69 6F 6E lication/ xml;version
0000008C 3D 31 0D 0A 43 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 68 3A 20 =1. . Content-Length:.
000000A0 32 36 31 0D 0A 43 6F 6E 74 65 6E 74 2D 54 79 70 65 3A 20 6D 261. . Content-Type:. m
000000B4 75 6C 74 69 70 61 72 74 2F 66 6F 72 6D 2D 64 61 74 61 3B 20 ultipart/ form-data;.
000000C8 62 6F 75 6E 64 61 72 79 3D 32 61 38 61 65 36 61 64 2D 66 34 boundary=2a8ae6ad-f4
000000DC 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 37 30 31 ad-4d9a-a92c-6d21701
000000F0 31 66 65 30 66 0D 0A 0D 0A 2D 2D 32 61 38 61 65 36 61 64 2D 1fe0f. . . . --2a8ae6ad-
00000104 66 34 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 37 f4ad-4d9a-a92c-6d217
00000118 30 31 31 66 65 30 66 0D 0A 43 6F 6E 74 65 6E 74 2D 44 69 73 011fe0f. . Content-Dis
0000012C 70 6F 73 69 74 69 6F 6E 3A 20 66 6F 72 6D 2D 64 61 74 61 3B position:. form-data;
00000140 20 6E 61 6D 65 3D 22 72 61 74 69 6E 67 56 61 6C 75 65 22 0D . name="ratingValue".
00000154 0A 0D 0A 31 30 30 0D 0A 2D 2D 32 61 38 61 65 36 61 64 2D 66 . . . 100. . --2a8ae6ad-f
00000168 34 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 37 30 4ad-4d9a-a92c-6d2170
0000017C 31 31 66 65 30 66 0D 0A 43 6F 6E 74 65 6E 74 2D 44 69 73 70 11fe0f. . Content-Disp
00000190 6F 73 69 74 69 6F 6E 3A 20 66 6F 72 6D 2D 64 61 74 61 3B 20 osition:. form-data;.
000001A4 6E 61 6D 65 3D 22 63 6F 6D 6D 65 6E 74 22 0D 0A 0D 0A 41 6C name="comment". . . . Al
000001B8 6C 65 73 25 32 30 4F 4B 25 32 30 2D 25 32 30 56 69 65 6C 65 les%20OK%20-%20Viele
000001CC 6E 25 32 30 44 61 6E 6B 0D 0A 2D 2D 32 61 38 61 65 36 61 64 n%20Dank. . --2a8ae6ad
000001E0 2D 66 34 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 -f4ad-4d9a-a92c-6d21
000001F4 37 30 31 31 66 65 30 66 2D 2D 7011fe0f--

07. 01. 2021 16:20:22 Response received:
HTTP/ 1. 1 200 OK

Server: nginx

Date: Thu, 07 Jan 2021 15:19:22 GMT

Content-Type: text/ xml; charset=UTF-8

Transfer-Encoding: chunked

Connection: keep-alive

Vary: Accept-Encoding

Cache-Control: no-cache, private

Set-Cookie: localization_currency=EUR; expires=Sun, 05-Jan-2031 15:19:22 GMT; Max-Age=315360000; path=/ ; httponly

Set-Cookie: localization_timezone=Europe%2FBerlin; expires=Sun, 05-Jan-2031 15:19:22 GMT; Max-Age=315360000; path=/ ; httponly

Set-Cookie: localization_locale=fr; expires=Sun, 05-Jan-2031 15:19:22 GMT; Max-Age=315360000; path=/ ; httponly

Set-Cookie: bluestorm=g8k254sjri4am3stt90mqsas6p; path=/ ; domain=. delcampe. net; HttpOnly

Cache-Control: max-age=0, must-revalidate, private

Expires: Thu, 07 Jan 2021 15:19:22 GMT

Strict-Transport-Security: max-age=15552000

X-Frame-Options: SAMEORIGIN



224

<?xml version="1. 0" encoding="UTF-8"?>
<Delcampe_Notification>
<Notification_Token></ Notification_Token>
<Notification_Datetime>2021-01-07 15:19:22</ Notification_Datetime>
<Notification_Data>
<Headers>
<Ressource>item-rating</ Ressource>
<Action>POST</ Action>
<Status>200</ Status>
</ Headers>
<body>
<feedback>
<status>Your request was taken into account!</ status>
</ feedback>
</ body>
</ Notification_Data>
</ Delcampe_Notification>

0



2.
We create and send a nonstandard complying request (content is longer than stated in Content-Length), we get a much more prompt response, with a status 200 XML response, but followed by an error "bad request" as HTML page (see below).

07. 01. 2021 16:59:02 Senging . . . .
Buffer:00000299AD825844 Position:00000202 AllocSize:640 UsedSize:514
00000000 50 4F 53 54 20 2F 69 74 65 6D 2F 31 31 33 33 32 37 30 34 36 POST. / item/ 113327046
00000014 34 2F 62 75 79 65 72 2F 72 61 74 69 6E 67 3F 74 6F 6B 65 6E 4/ buyer/ rating?token
00000028 3D 62 39 65 61 39 31 31 30 34 63 34 34 39 35 30 33 64 31 62 =b9ea91104c449503d1b
0000003C 31 62 64 39 30 39 30 39 32 38 38 65 31 20 48 54 54 50 2F 31 1bd90909288e1. HTTP/ 1
00000050 2E 31 0D 0A 48 6F 73 74 3A 20 72 65 73 74 2E 64 65 6C 63 61 . 1. . Host:. rest. delca
00000064 6D 70 65 2E 6E 65 74 0D 0A 41 63 63 65 70 74 3A 20 61 70 70 mpe. net. . Accept:. app
00000078 6C 69 63 61 74 69 6F 6E 2F 78 6D 6C 3B 76 65 72 73 69 6F 6E lication/ xml;version
0000008C 3D 31 0D 0A 43 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 68 3A 20 =1. . Content-Length:.
000000A0 32 36 31 0D 0A 43 6F 6E 74 65 6E 74 2D 54 79 70 65 3A 20 6D 261. . Content-Type:. m
000000B4 75 6C 74 69 70 61 72 74 2F 66 6F 72 6D 2D 64 61 74 61 3B 20 ultipart/ form-data;.
000000C8 62 6F 75 6E 64 61 72 79 3D 32 61 38 61 65 36 61 64 2D 66 34 boundary=2a8ae6ad-f4
000000DC 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 37 30 31 ad-4d9a-a92c-6d21701
000000F0 31 66 65 30 66 0D 0A 0D 0A 2D 2D 32 61 38 61 65 36 61 64 2D 1fe0f. . . . --2a8ae6ad-
00000104 66 34 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 37 f4ad-4d9a-a92c-6d217
00000118 30 31 31 66 65 30 66 0D 0A 43 6F 6E 74 65 6E 74 2D 44 69 73 011fe0f. . Content-Dis
0000012C 70 6F 73 69 74 69 6F 6E 3A 20 66 6F 72 6D 2D 64 61 74 61 3B position:. form-data;
00000140 20 6E 61 6D 65 3D 22 72 61 74 69 6E 67 56 61 6C 75 65 22 0D . name="ratingValue".
00000154 0A 0D 0A 31 30 30 0D 0A 2D 2D 32 61 38 61 65 36 61 64 2D 66 . . . 100. . --2a8ae6ad-f
00000168 34 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 37 30 4ad-4d9a-a92c-6d2170
0000017C 31 31 66 65 30 66 0D 0A 43 6F 6E 74 65 6E 74 2D 44 69 73 70 11fe0f. . Content-Disp
00000190 6F 73 69 74 69 6F 6E 3A 20 66 6F 72 6D 2D 64 61 74 61 3B 20 osition:. form-data;.
000001A4 6E 61 6D 65 3D 22 63 6F 6D 6D 65 6E 74 22 0D 0A 0D 0A 41 6C name="comment". . . . Al
000001B8 6C 65 73 25 32 30 4F 4B 25 32 30 2D 25 32 30 56 69 65 6C 65 les%20OK%20-%20Viele
000001CC 6E 25 32 30 44 61 6E 6B 0D 0A 2D 2D 32 61 38 61 65 36 61 64 n%20Dank. . --2a8ae6ad
000001E0 2D 66 34 61 64 2D 34 64 39 61 2D 61 39 32 63 2D 36 64 32 31 -f4ad-4d9a-a92c-6d21
000001F4 37 30 31 31 66 65 30 66 2D 2D 0D 0A 0D 0A 7011fe0f--. . . .
07. 01. 2021 16:59:07 Response received:
HTTP/ 1. 1 200 OK

Server: nginx

Date: Thu, 07 Jan 2021 15:59:03 GMT

Content-Type: text/ xml; charset=UTF-8

Transfer-Encoding: chunked

Connection: keep-alive

Vary: Accept-Encoding

Cache-Control: no-cache, private

Set-Cookie: localization_currency=EUR; expires=Sun, 05-Jan-2031 15:59:03 GMT; Max-Age=315360000; path=/ ; httponly

Set-Cookie: localization_timezone=Europe%2FBerlin; expires=Sun, 05-Jan-2031 15:59:03 GMT; Max-Age=315360000; path=/ ; httponly

Set-Cookie: localization_locale=fr; expires=Sun, 05-Jan-2031 15:59:03 GMT; Max-Age=315360000; path=/ ; httponly

Set-Cookie: bluestorm=e1098btkhru66q138h86urr190; path=/ ; domain=. delcampe. net; HttpOnly

Cache-Control: max-age=0, must-revalidate, private

Expires: Thu, 07 Jan 2021 15:59:03 GMT

Strict-Transport-Security: max-age=15552000

X-Frame-Options: SAMEORIGIN



224

<?xml version="1. 0" encoding="UTF-8"?>
<Delcampe_Notification>
<Notification_Token></ Notification_Token>
<Notification_Datetime>2021-01-07 15:59:03</ Notification_Datetime>
<Notification_Data>
<Headers>
<Ressource>item-rating</ Ressource>
<Action>POST</ Action>
<Status>200</ Status>
</ Headers>
<body>
<feedback>
<status>Your request was taken into account!</ status>
</ feedback>
</ body>
</ Notification_Data>
</ Delcampe_Notification>

0



HTTP/ 1. 1 400 Bad Request

Server: nginx

Date: Thu, 07 Jan 2021 15:59:03 GMT

Content-Type: text/ html

Content-Length: 166

Connection: close



<html>

<head><title>400 Bad Request</ title></ head>

<body bgcolor="white">

<center><h1>400 Bad Request</ h1></ center>

<hr><center>nginx</ center>

</ body>

</ html>


We have tried various scenarios, but the issue remains the same. We either get a quick response followed by a HTML "bad request" or we get a delayed (~ 60 seconds) one, without that.

Hello klaus_schneider,

The dumps are not readable. Did you try to send a request with a third party software such as Postman?

I have tested on my side, I don't have any delay when I send requests.

Best Regards,
--
Thomas
Delcampe Team

Hi there,
January is unfortunately a bad month for such problems, a lot of administrative things have to be done. I will try to find out more information about the problem as soon as possible. I think it is due to the coordination between the load balancer and the actual server with you. It also happens again and again that an OK request comes from the server and then a bad request from the load balancer. We use our own software, not postman or similar. The 60 seconds are certainly a timeout from the server. Probably something is still expected or PHP ignores the bad request ... More information shortly.
Kind regards