12-04-2010 06:34 PM - edited 12-04-2010 06:58 PM
HI all.
I use dynamic licensing and my servers authorize HTTP POST from
this IP address:
208.65.74.0/24
208.65.73.0/24
Today I received an HTTP POST from this IP address and my server rejected the HTTP POST:
208.65.78.13
Is this normal?
Why app world doesn't told us that they changed IP address?
I'm sure that like me, many many developers here will have the same problem.
Solved! Go to Solution.
12-05-2010 05:12 AM - edited 12-05-2010 05:55 AM
My server is blocking tons of request from this IP Address:
208.65.78.13
I'm loosing money, who will give me this money back?
Is this IP authorized to generate request on my server?
I'm really disappointed with RIM now, they can't change IP to their servers without informing us previously, really bad way to proceed, really disappointed.
Now I don't know if authorize or not that IP address and I don't know if the HTTP POST are fraudolent or legal.
12-05-2010 09:03 AM
Well it seems highly probable they are from rim given they are in a similar range.
Just authorise it.
I dont think RIM gave us a promise the IP addreses wouldnt change or said anything of the sort. I agree there is a potential security risk but at the moment that's our only choice.
12-05-2010 11:04 AM
RIM knows that we use this method to try to protect the HTTP POST, at least a communication in the developer world.
What happened to the HTPP POST that I blocked and don't answered with an activation code?
Customers have been credited for the transactions or not?
12-06-2010 10:11 AM
Hi all,
The new IP address ranges have been posted in the Vendor Portal. Simply log into the Vendor Portal using your account credentials to see the new ranges you can expect when using Dynamic Licensing.
12-06-2010 10:31 AM
Every time I see Ryan, you bring good news,
really thanks Ryan!
12-06-2010 10:37 AM
I could be wrong but this is the first time I've seen an offical range of IP address posted for us to filter against. I mean, yes, we all knew what the IP address was before but now it is finally blessed.
12-06-2010 11:00 AM
you are not wrong rlord but developers that asked to developers support how to protect HTTP POST
received the suggestions to use this way in addition to others method.
12-06-2010 12:17 PM
Yes. I also contacted developer support about the IP's but I'm glad they are officially announcing it to all the developers and not just these one-offs.
Communication is key and if other changes were posted on the vendor portal, it would avoid some of these posts. I'm not even getting emails when new phones are released anymore! ![]()
12-06-2010 12:30 PM
RLord321 wrote:
Communication is key and if other changes were posted on the vendor portal, it would avoid some of these posts. I'm not even getting emails when new phones are released anymore!
I agree and quote it.