Twitter UI is not creating cookies over several users under proxy network infrastructures

[cmonge]

We have a network topology where many users access twitter from a proxy server. We have noticed that several users are not able to load tweets without being logged in. The main difference is that the gt cookie is not being created and the call which tries to create it returns a 429 status code. This is not happening outside our network topology and we haven’t found any documentation about this situation and it seems to be there is not an easy way to get out of this status. Could you please give us some guideline to solve this problem?

[andypiper]

This is not really a developer API problem and we don’t specifically support this. Can you be more specific? There’s no guarantee that we can help here. Can you describe in enough detail for us to reproduce?

[cmonge]

Hello Andy
Thanks for the quick response. Actually it is hard to reproduce outside proxy environments, please find below how we reproduce the problem:
1 - Clear cookies and cache.
2 - Close the browser.
3 - Open a twitter link coming from a third party app (Email client for example).
Results:

• The tweet is not loaded and we can see some errors from calls to the API (/1.1/guest/activate.json), please find below an screenshot.
  

  
  .

• The real difference between a successful call is a cookie called “gt” created by this post call.

• We also noticed that Twitter html code returns a script to create this cookie on regular basis but the script is not returned under this network infrastructure (Our organization has hundred of users accessing twitter over this topology).

PD: Currently we use the twitter’s api for some other features and it seems to be we are getting throttled by this api call (At least this is what I can extract from the 429 status code from the network logs). I tried to find any documentation about the guest endpoint but it seems to be this is not a public endpoint. Do you know if the premium api access would help us on this case? I am not sure if there is a way twitter can white list a server. I feel like due to all our users are accessing twitter from a proxy node would be generating this problem.

Thanks in advance!