you mean that PR8 of that verified URL is not checked in PR Emulator? Might be, because SER still had that PR value from somewhere else (cache, PR from engine directly...).
Sorry for not answering this. I think it was later resolved by email or via private message. However, a customer also has problems getting this to work. @VMart did you remember what problem it was and how it was solved?
Could it have been the PR Emulator not binding correctly on 127.0.0.1:80 ?
Comments