For dev work like this I find fiddler really useful, it lets you temporarily proxy specific ports paths etc., replace a server script with a locally hosted one and even decrypt https traffic. On Jun 17, 2012 9:59 PM, "Joseph Lust" <[email protected]> wrote:
> Excellent points Thomas. > > My point here is that when you're given a few hours to accomplish > something and wind up slamming against the SOP, it is easier to just > disable it, do your thing, and put it back. Were I to work with the problem > I described for a while, I'd look into the proxy or other options, but I > just wanted to posit this as a possible temporary work around given that a > number of people seem to be running into this. > > Of course, I know my suggestion is like noting that your hand gun might > fire faster if you take the safety mechanism out. :) Though, in the case of > FF prompting to allow cross site access for a page, it is not as dangerous > and provides a quick dev workaround. > > > Joe > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/HDznupahr_AJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
