Current time: 12-19-2017, 12:49 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Potential issue in EU
10-03-2017, 02:09 AM
Post: #1
Potential issue in EU
Hello.

I'm using the same script in EU and US. In US it works as it should, in EU it fails to setDnsName to what I needed to be. Here is the script

setDnsName http://www.example.de network.example.net
navigate https://www.example.de

When routing via network.example.net there is a specific set of unique headers and I see those when selecting US based test locations and I don't see them when selecting EU based test locations
Find all posts by this user
Quote this message in a reply
10-04-2017, 02:55 AM
Post: #2
RE: Potential issue in EU
Any locations specifically? It's possible that setDnsName isn't supported yet in the new agent and that is probably causing it. If you use setDns to set the IP instead it should work.

I'll see if there is anything interesting I can do to get setDnsName working in the new agent
Visit this user's website Find all posts by this user
Quote this message in a reply
10-04-2017, 10:42 AM
Post: #3
RE: Potential issue in EU
Hi Patrick.

I tried Frankfurt, AWS; Amsterdam; London
Find all posts by this user
Quote this message in a reply
10-13-2017, 11:54 PM
Post: #4
RE: Potential issue in EU
I think all of those are on the new agent. FWIW, I rolled out setDnsName support in the new agent a few days ago so it should work now.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)