| # |
Dec 5th 2017, 15:11 |
 pedroseco |
just have to disable the av to see if it is blocking somehow. |
| # |
Dec 5th 2017, 15:11 |
hmic |
not that the user in question is on an error path on the server, which leads to the text/html response? |
| # |
Dec 5th 2017, 15:11 |
pedroseco |
yes, since I can do this via curl on the console. |
| # |
Dec 5th 2017, 15:10 |
hmic |
and you are sure the server is responding with (the correct) data? |
| # |
Dec 5th 2017, 15:10 |
pedroseco |
on my machine and others, it's never text/html and always application/json |
| # |
Dec 5th 2017, 15:10 |
hmic |
ok |
| # |
Dec 5th 2017, 15:10 |
pedroseco |
and the request is "application/json, text/javascript, */*; q=0.01" |
| # |
Dec 5th 2017, 15:09 |
pedroseco |
ok so the response of the content-type is: text/html; charset=UTF-8 |
| # |
Dec 5th 2017, 15:08 |
hmic |
no proxy is setup? |
| # |
Dec 5th 2017, 15:08 |
hmic |
you've checked request and response headers? |
| # |
Dec 5th 2017, 15:08 |
pedroseco |
first disabeling it. |
| # |
Dec 5th 2017, 15:07 |
pedroseco |
so I'll go check for the AV |
| # |
Dec 5th 2017, 15:07 |
pedroseco |
yup that's true |
| # |
Dec 5th 2017, 15:07 |
hmic |
if the response is empty, not valid json. thats what you expect |
| # |
Dec 5th 2017, 15:06 |
hmic |
which is fine |
| # |
Dec 5th 2017, 15:06 |
pedroseco |
this because it returns a empty json data. |
| # |
Dec 5th 2017, 15:06 |
pedroseco |
ok so the "official" error on chrome is this: Ajax Load Error - Connection Error: 200 SyntaxError: JSON.parse: unexpected end of data at line 2 column 1 of the JSON data |
| # |
Dec 5th 2017, 15:00 |
hmic |
so check - on the network tab - the request and response on a non-working vs. working system |
| # |
Dec 5th 2017, 15:00 |
pedroseco |
but its the same on chrome or firefox so not sure about the plugin |
| # |
Dec 5th 2017, 14:59 |
pedroseco |
ok let me check. |
| # |
Dec 5th 2017, 14:59 |
hmic |
accepts header that is |
| # |
Dec 5th 2017, 14:59 |
hmic |
- can be some plugin or other setting |
| # |
Dec 5th 2017, 14:59 |
hmic |
can also be the wrong accepts being sent by the browsers |
| # |
Dec 5th 2017, 14:57 |
pedroseco |
ok but let me check the AV |
| # |
Dec 5th 2017, 14:55 |
pedroseco |
but it does :| |
| # |
Dec 5th 2017, 14:55 |
pedroseco |
this didn't work on IE |
| # |
Dec 5th 2017, 14:55 |
pedroseco |
I would look into that if |
| # |
Dec 5th 2017, 14:55 |
pedroseco |
nice point |
| # |
Dec 5th 2017, 14:54 |
hmic |
anti virus |
| # |
Dec 5th 2017, 14:54 |
hmic |
many things interfere with the browser in a typical windows environment |
| # |
Dec 5th 2017, 14:54 |
pedroseco |
AV issue? |
| # |
Dec 5th 2017, 14:54 |
hmic |
can be an AV issue e.g., or proxy or... |
| # |
Dec 5th 2017, 14:54 |
pedroseco |
with autentication, but yes |
| # |
Dec 5th 2017, 14:53 |
pedroseco |
different clients |
| # |
Dec 5th 2017, 14:53 |
hmic |
is it public? |
| # |
Dec 5th 2017, 14:53 |
pedroseco |
same source |
| # |
Dec 5th 2017, 14:53 |
pedroseco |
yes |
| # |
Dec 5th 2017, 14:53 |
hmic |
the one that works and the one that does not? |
| # |
Dec 5th 2017, 14:53 |
pedroseco |
yes same |
| # |
Dec 5th 2017, 14:53 |
pedroseco |
that's the only place where this JSON issue happens. |
| # |
Dec 5th 2017, 14:53 |
hmic |
so you are accessing the same server? |