Are you able to set up a DNS wildcard that is only visible internally but which uses a valid TLD? We use a DNS wildcard for exactly this reason, to point to a specific internal IP to satisfy Google's oAuth requirements. e.g. *.dev.wit-internal.edu.au could point to your dev server, and each site in IIS could have a host header registered against it (such as internet.dev.wit-internal.edu.au). Alternatively, for testing you could just set up a host file on your own machine (and add the appropriate matching host header to the site in IIS) if this is just a once-off app that you need to test it with.
On Tuesday, March 5, 2013 1:48:48 PM UTC+11, Mark Picker wrote: > > Tell me about. It means I can't test this as I'm not keen on deploying it > to production until I know it works in our environment :( -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry --- You received this message because you are subscribed to the Google Groups "farcry-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
