G
|trim|replace(" ", "")Size: a a a
2019 October 01
G
split("₽")[0] можно ещёG
тогда можно будет через numeric_state сверять
below: xxxDD
DD
Не хочет((
G
скопируй строку что он получил?
DD
скопируй строку что он получил?
5 767 ₽
DD
выглядит как пробел
DD
Или что скопировать?))
G
ну ты просто с пробелами уже скопировал
G
ща погодь
G
НВ
Может кто-нибудь курлом дернуть один адрес?
Какой ответ придет?
curl -v -X POST -d '{"slid_token":"123:123"}' https://developer.starline.ru/json/v2/auth.slidКакой ответ придет?
DD
Эт да я тоже вижу, что сделать не пойму
G
вон там лежит уже в json всё
DD
Может кто-нибудь курлом дернуть один адрес?
Какой ответ придет?
curl -v -X POST -d '{"slid_token":"123:123"}' https://developer.starline.ru/json/v2/auth.slidКакой ответ придет?
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 185.129.96.82...
* TCP_NODELAY set
* Connected to developer.starline.ru (185.129.96.82) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=RU; postalCode=194044; ST=Leningrag; L=St. Petersburg; street=d. 9 litera A ofis 204, ul. Komissara Smirnova; O=LLC StarLine; OU=job; OU=PremiumSSL Wildcard; CN=*.starline.ru
* start date: May 23 00:00:00 2018 GMT
* expire date: Jun 3 23:59:59 2020 GMT
* subjectAltName: host "developer.starline.ru" matched cert's "*.starline.ru"
* issuer: C=RU; ST=Moscow; L=Moscow; O=RU-Center (\U0417\U0410\U041E \U0420\U0435\U0433\U0438\U043E\U043D\U0430\U043B\U044C\U043D\U044B\U0439 \U0421\U0435\U0442\U0435\U0432\U043E\U0439 \U0418\U043D\U0444\U043E\U0440\U043C\U0430\U0446\U0438\U043E\U043D\U043D\U044B\U0439 \U0426\U0435\U043D\U0442\U0440); CN=RU-CENTER High Assurance Services CA 2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55a493e00580)
> POST /json/v2/auth.slid HTTP/2
> Host: developer.starline.ru
> User-Agent: curl/7.58.0
> Accept: */*
> Content-Length: 24
> Content-Type: application/x-www-form-urlencoded
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* We are completely uploaded and fine
< HTTP/2 429
< server: nginx
< date: Tue, 01 Oct 2019 07:49:30 GMT
< content-length: 52
< strict-transport-security: max-age=31536000; includeSubDomains; preload
<
{
"code" : 429,
"codestring" : "Exceeding limit"
* Connection #0 to host developer.starline.ru left intact
DD
value_json пробовать?
НВ
Не хочет((
{{ "5 353 Р" | trim | replace(" ", "") | replace("Р", "") | float }}
НВ
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 185.129.96.82...
* TCP_NODELAY set
* Connected to developer.starline.ru (185.129.96.82) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=RU; postalCode=194044; ST=Leningrag; L=St. Petersburg; street=d. 9 litera A ofis 204, ul. Komissara Smirnova; O=LLC StarLine; OU=job; OU=PremiumSSL Wildcard; CN=*.starline.ru
* start date: May 23 00:00:00 2018 GMT
* expire date: Jun 3 23:59:59 2020 GMT
* subjectAltName: host "developer.starline.ru" matched cert's "*.starline.ru"
* issuer: C=RU; ST=Moscow; L=Moscow; O=RU-Center (\U0417\U0410\U041E \U0420\U0435\U0433\U0438\U043E\U043D\U0430\U043B\U044C\U043D\U044B\U0439 \U0421\U0435\U0442\U0435\U0432\U043E\U0439 \U0418\U043D\U0444\U043E\U0440\U043C\U0430\U0446\U0438\U043E\U043D\U043D\U044B\U0439 \U0426\U0435\U043D\U0442\U0440); CN=RU-CENTER High Assurance Services CA 2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55a493e00580)
> POST /json/v2/auth.slid HTTP/2
> Host: developer.starline.ru
> User-Agent: curl/7.58.0
> Accept: */*
> Content-Length: 24
> Content-Type: application/x-www-form-urlencoded
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* We are completely uploaded and fine
< HTTP/2 429
< server: nginx
< date: Tue, 01 Oct 2019 07:49:30 GMT
< content-length: 52
< strict-transport-security: max-age=31536000; includeSubDomains; preload
<
{
"code" : 429,
"codestring" : "Exceeding limit"
* Connection #0 to host developer.starline.ru left intact
Спасибо
НВ
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 185.129.96.82...
* TCP_NODELAY set
* Connected to developer.starline.ru (185.129.96.82) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=RU; postalCode=194044; ST=Leningrag; L=St. Petersburg; street=d. 9 litera A ofis 204, ul. Komissara Smirnova; O=LLC StarLine; OU=job; OU=PremiumSSL Wildcard; CN=*.starline.ru
* start date: May 23 00:00:00 2018 GMT
* expire date: Jun 3 23:59:59 2020 GMT
* subjectAltName: host "developer.starline.ru" matched cert's "*.starline.ru"
* issuer: C=RU; ST=Moscow; L=Moscow; O=RU-Center (\U0417\U0410\U041E \U0420\U0435\U0433\U0438\U043E\U043D\U0430\U043B\U044C\U043D\U044B\U0439 \U0421\U0435\U0442\U0435\U0432\U043E\U0439 \U0418\U043D\U0444\U043E\U0440\U043C\U0430\U0446\U0438\U043E\U043D\U043D\U044B\U0439 \U0426\U0435\U043D\U0442\U0440); CN=RU-CENTER High Assurance Services CA 2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55a493e00580)
> POST /json/v2/auth.slid HTTP/2
> Host: developer.starline.ru
> User-Agent: curl/7.58.0
> Accept: */*
> Content-Length: 24
> Content-Type: application/x-www-form-urlencoded
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* We are completely uploaded and fine
< HTTP/2 429
< server: nginx
< date: Tue, 01 Oct 2019 07:49:30 GMT
< content-length: 52
< strict-transport-security: max-age=31536000; includeSubDomains; preload
<
{
"code" : 429,
"codestring" : "Exceeding limit"
* Connection #0 to host developer.starline.ru left intact
Апи старлайна дурно пахнет. Второй день какие-то ошибки возвращает