Volver a todas las conversaciones
You left a PHP print_r in your production code, and the API is broken
ornicar
4 years ago
Array
(
[valid] => 1
[block] => 0
[disposable] => 0
[domain] => ciclomed.com.br
[text] => Looks okay
[reason] => Heuristics: WM1
[risk] => 10
[mx_host] => aspmx.l.google.com
[possible_typo] =>
[mx_ip] => 173.194.73.27
[mx_info] => Using MX pointer aspmx.l.google.com from DNS with priority: 1
[last_changed_at] => 2020-04-28T00:18:15+02:00
)
Is what I get from your JSON endpoint. Since it’s not valid JSON (but a PHP print_r output) it renders the API unusable.
It has been happening for 2 days now, on about 33% of the requests.
Únase a la conversación, añada un comentario a continuación:
Inicie sesió/Regístrese para publicar nuevos comentarios
I’m still seeing invalid JSON responses on a percentage of our requests.
Hi!
Thanks for the report! We’re doing a major overhaul of the backend, and apparently some of the API endpoints were left in a weird state.
It should be fixed now. Thanks again!