InfoPath Dev

I am getting the Infopath security notice "This form is located at an Internet location etc." and can't access my web service.  I am testing this all on my local home PC, the form is published to c:\temp and the web service is running on http://localhost:1234

 Can someone please explain why IP thinks it's on the Internet and what I need to do here?

 Thanks in advance

Graeme:

the form is published to c:\temp

May I ask what is the sense of publishing a template to a local folder which is accessible only locally?
Publishing implies to be to location accessible over network like share folder, sharepoint form library, etc.

Graeme:

I am getting the Infopath security notice "This form is located at an Internet location etc." and can't access my web service. 

The text of error is misleading.

This error text is usually shown when I try to preview by F5 any Infopath template locally which accesses external data source/connection (for ex., web service). In such cases (testing, prototyping, usually without any publishing) I attribute to my Infopath XSN template the Full Trust and digitally sign it (in Infopath Designer 2010, File on ribbon > Info > Form Options > Security and Trust)

Only publishing locally because I am testing stuff at home and have no network.

I suppose I can create a cert and sign the form, but my question is - why should I need to? Everything is on the same PC/domain.

Graeme:

Only publishing locally because I am testing stuff at home and have no network

IMO, there is no need to publish template if you do not have network

If template is in environment that has no network, it does not mean the same computer since it still can be distributed (through a pen drive, diskettes, etc.).

It is how Microsoft determined and you should have asked it Microsoft. I did it few times, check, for example (might be I did not formulate it concisely but the main question was why and what is the sense of more rigid security restrictions when developing/testing purely on a local machine):

• Gennady Vanin. Why Infopath 2010 client form with custom code requires Full Trust and can't be run with Domain or Restricted security level? 
  http://social.technet.microsoft.com/Forums/en-US/sharepoint2010customization/thread/4a3de61e-c16f-4d8c-8597-e9ca5d1d709d/
  
  
• Gennady Vanin. How to create/use in Infopath 2010 client forms a manual (wizard) data connection to sharepoint online lists without being deadlocked to attribute to forms the Full Trust security level?
  
  http://community.office365.com/en-us/forums/171/p/59016/217021.aspx#217021
  
  
• Gennady Vanin. What's the sense in forcing to digitally sign the Infopath 2010 forms?
  http://sharepoint.stackexchange.com/questions/39970/whats-the-sense-in-forcing-to-digitally-sign-the-infopath-2010-forms
  
  
• etc.
  
  

Graeme:

why should I need to? Everything is on the same PC/domain

Because Microsoft determined it so. 

The rationale is probably the same as for Loopback Security Authentication fix:

• You receive error 401.1 when you browse a local Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version
  
  "This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
  
  Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected"
  
  "CAUSE
  This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name"
  
  
• Disable LoopbackCheck & SharePoint: What every admin and developer should know
• SharePoint – Disable LoopBack Check
  
• etc.
  

Search internet and you find a lot of invoked inconveniences and collateral problems (with completely inconclusive, unrelated and misleading error messages) in development and production environments