Your IP. In JSON • Hacker News Board

Re: Your IP. In JSON

#31

Post by ssdghjyt » Wed, Mar 02, 2011, 12:27 PM UTC

Click on our website:

╭══════════════╮ http://simurl.com/voblec ╰══════════════╯

Website wholesale various fashion shoes, such as Nike, Jordan, prada, also includes the jeans, shirt, bags, hats and decoration. Personality manufacturing execution systems (Mes) clothing, Grab an eye bag coat + tide bag

Air jordan(1-24)shoes $30

Handbags(Coach l v f e n d i d&g) $35

Tshirts (Polo ,ed hardy,lacoste) $15

Jean(True Religion,ed hardy,coogi) $30

Sunglasses(Oakey,coach,gucci,A r m a i n i) $15

New era cap $12

Bikini (Ed hardy,polo) $20

accept paypal and free shipping

╭══════════════╮ http://simurl.com/voblec ╰══════════════╯

Re: Your IP. In JSON

#32

Post by mryall » Wed, Mar 02, 2011, 1:16 PM UTC

maggit wrote: post #22

enneff wrote: post #12

Earlier quoted context omitted.

"I'm not sure that reporting [only] an IPv6 address is all that useful" Why not? It's useful to me, and anyone else who has an IPv6 address. The future is now. Get with the program.

I'm not in the future yet, but I was under the impression that with IPv6 you would actually know your own public address, because there is no need for NAT. Is this not correct?

Not only do you know it, you get it tattooed on your body. If there's no need to change IP addresses, you might as well make it permanent.

Re: Your IP. In JSON

#33

Post by nphase » Wed, Mar 02, 2011, 1:37 PM UTC

Also, icanhazip.com

Re: Your IP. In JSON

#34

Post by sghael » Wed, Mar 02, 2011, 1:39 PM UTC

mike-cardwell wrote: post #20

Some suggestions: Make jsonip.com dual stack IPv4/IPv6 and work for IPv6 addresses too. Return some other useful IP information, such as the PTR, the domain name part of the PTR, and the country code and name. Example: https://grepular.com/ipinfo EDIT: Don't use that URL for your own stuff or I'll block it. I only put it there as an example of how the JSON should be returned. EDIT2: Might be useful if it included the…

This brings up something I'm waffling on. Whats the correct content type for JSON?

in your example returning "Content-Type: text/plain; charset=UTF-8" which is nice because FF knows to render it in the browser (good for debugging atleast).

But votes on SO seem to indicate it should be "application/json"

http://stackoverflow.com/questions/477816/the-right-json-con...

Re: Your IP. In JSON

#35

Post by powertower » Wed, Mar 02, 2011, 2:00 PM UTC

http://myip.wampdeveloper.com/

Only the ip, no html tags, no formating, nothing but 1 string returned.

Also correctly deals with x-forwarded-for and all the other client/proxy/remote header fields.

Absolute minimum way of returning an IP address.

Re: Your IP. In JSON

#36

Post by dedward » Wed, Mar 02, 2011, 2:01 PM UTC

maggit wrote: post #22

enneff wrote: post #12

Earlier quoted context omitted.

"I'm not sure that reporting [only] an IPv6 address is all that useful" Why not? It's useful to me, and anyone else who has an IPv6 address. The future is now. Get with the program.

I'm not in the future yet, but I was under the impression that with IPv6 you would actually know your own public address, because there is no need for NAT. Is this not correct?

True in theory, likely in practice.

NAT will still be possible - just not necessary for conserving address space.

But... imagine trying to get your call-center staff to ask the customer to read back their local IPv6 address so you can troubleshoot. That's going to be bad enough. Then consider there may be proxies in the way, intentionally or otherwise, so you probably want to know the IP address the customer is hitting your product with, not their computer.

Most of us on HN are probably smart enough to find out our own IPs a half dozen ways - it's the 3rd party support that's tougher.

Re: Your IP. In JSON

#37

Post by NovaDesu » Wed, Mar 02, 2011, 2:02 PM UTC

qixxiq wrote: post #13

rburgt wrote: post #3

Earlier quoted context omitted.

its there already: http://jsonip.com/nameofcallbackfunction

You should probably include the ?callback= functionality anyway. A great deal of libraries assume it will be a get variable, and cater for it specially i.e. jQuery with http://jsonip.com/?callback= ?

I actually made something like this a while ago.

http://demontunes.com/api/?g=ip // plain ip

http://demontunes.com/api/?g=ip&format=json // in json

http://demontunes.com/api/?g=ip&format=json&callback... // with a callback

Re: Your IP. In JSON

#38

Post by NovaDesu » Wed, Mar 02, 2011, 2:03 PM UTC

IsaacSchlueter wrote: post #10

hm2k wrote: post #8

http://whatismyip.akamai.com/ Pretty reliable.

Parsing text is too hard. It'd be easier if it was in JSON.

http://demontunes.com/api/?g=ip&format=json (&callback=name)

Re: Your IP. In JSON

#39

Post by dedward » Wed, Mar 02, 2011, 2:04 PM UTC

billpg wrote: post #7

Is there an HTTPS service planned? Without it, you may just be seeing the IP of a transparent proxy server.

Which might be exactly what you want if you are troubleshooting HTTP issues with customers "Go to page X and tell me what it says" rather than "what is your IP" is much more reliable.

If there's a proxy, there's a proxy - but I can't troubleshoot the customer's connectivity issue without that.

Re: Your IP. In JSON

#40

Post by JoachimSchipper » Wed, Mar 02, 2011, 2:06 PM UTC

mryall wrote: post #32

maggit wrote: post #22

Earlier quoted context omitted.

I'm not in the future yet, but I was under the impression that with IPv6 you would actually know your own public address, because there is no need for NAT. Is this not correct?

Not only do you know it, you get it tattooed on your body. If there's no need to change IP addresses, you might as well make it permanent.

IPv6 addresses are statically allocated (well, in the IPv6 proponents' designs - in reality, we may end up with DHCPv6 and the like), but almost always provider-allocated (PA), not provider independent (PI); so you'll have to give it back to your ISP when you switch.

This is a good thing, by the way; PI space consumes memory on the backbone routers (they can't just send it to your ISP, after all - the whole point is that you can take it with you). Of course, PA space is just part of a larger allocation to your provider.

In other words, don't get the tattoo.