BT DSL Address checker not working

Is it me, or it the address checker not working?

404 errors on address and postcode checker at the moment

It is working now.

Not for me - still seeing 404 errors.

All three, phone, postcode and address are fine here - have just tried again.

.

Can you post the link you are using to the address checker, please?

http://www.dslchecker.bt.com/adsl/ADSLChecker.address

Although I normally go to the DSL Checker at http://dslchecker.bt.com/ first and select the Address link.

In reply to a post by MHC:

http://www.dslchecker.bt.com/adsl/ADSLChecker.address

That returns

Not Found

The requested URL /adsl/ADSLChecker.address was not found.

I did a cut and paste from the address bar after accessing the page. But did not check what was pasted!


www.dslchecker.bt.com/adsl/ADSLChecker.address is what appears in the address bar ... but if I cut and paste from here I get 404 too! Something odd happening somewhere,


Have you tried going through: http://www.dslchecker.bt.com/adsl/adslchecker.welcome?

That seems to work from this link.

Another mess up from BT Wholesales (useless)

Just keep out of it.


And where is the proof that it is a BT issue? You have none



You think you are always so perfect ... and whinge and whine when you lose 1 bit per second from your speed.

Edited by MHC (Sun 11-Sep-16 12:24:38)

I think BTW are fed up with me kept checking it every hour! LOL

Looks like that 404 has been hard-coded and they're now using some Javascript to enforce the http_referer.

For a while I found I had to use http://www.dslchecker.bt.com/adsl/ADSLChecker.Addres... rather than without the "output", but that also now gives 404.

At least when you do get to it the entry of just the postcode still gets you the address list.

In reply to a post by MHC:

www.dslchecker.bt.com/adsl/ADSLChecker.address is what appears in the address bar ... but if I cut and paste from here I get 404 too! Something odd happening somewhere,

That page requires the HTTP POST method, the HTTP GET method returns 404. Pasting the address into the address bar makes it an HTTP GET.

Using the following also still works for address (though using the telephone number parameter input as a get response no longer works)

..../adsl/ADSLChecker.AddressOutput?Buildingname=<building name>&Postcode=<postcode>

It's still been changed. It worked before, with the "Output" on the end as I posted.

I think BTW have updated the checker to do more checks so that its harder to link into their checker.

You cannot directly go to the following pages:
http://dslchecker.bt.com/adsl/ADSLChecker.telephone
or
http://dslchecker.bt.com/adsl/ADSLChecker.address

You have to go via http://dslchecker.bt.com/

That works for me.

*** update ***
Yep, it seems that BTW have change the checker to be more strict of how the requests are made.
Before your could just use GET Requests all over the place so a single line can do the actual check, that now requires a POST request.

My App still works as I was always using the correct way of requesting, however I don't think the single line linking of a check will work now.

Its a shame

Paul

Edited by PaulKirby (Sun 11-Sep-16 19:20:42)

In reply to a post by Oliver341:

In reply to a post by MHC:

www.dslchecker.bt.com/adsl/ADSLChecker.address is what appears in the address bar ... but if I cut and paste from here I get 404 too! Something odd happening somewhere,

That page requires the HTTP POST method, the HTTP GET method returns 404. Pasting the address into the address bar makes it an HTTP GET.

Agreed

It was due to they were using REQUEST which returns submitted GET and POST information which is lazy and bad.
It seems that they have corrected that mistake by using POST requests where it should.

Paul

I did have a gut feel that there was something going on in the background. I did hear though a "grapevine" that at times it was being hammered by automated requests from specific parties.

In reply to a post by MHC:

I did have a gut feel that there was something going on in the background. I did hear though a "grapevine" that at times it was being hammered by automated requests from specific parties.

I know I use to be one of them LOL
It got to a point where they would block our connections IP from being able to do requests, this was why I wasn't too fussed in our bad connection that use to drop our connection every few hours

I actually just checked my app etc, and it seems that's now not working, so I will have to look into what exactly they are checking.

Paul

My follow that page is not working as well.........

Can it do a post?

In reply to a post by BatBoy:

Can it do a post?

My App uses post and its broken.
It might need to be done in multiple requests, ill look into it.

Paul

In reply to a post by ian007jen:

My follow that page is not working as well.........

yeah, that's due to it calls it directly.

Paul