AnsweredAssumed Answered

Insert From URL returns bogus "Validation" errors for some urls

Question asked by nickorr on Mar 11, 2013
Latest reply on Jul 22, 2014 by TSGal

Summary

Insert From URL returns bogus "Validation" errors for some urls

Product

FileMaker Pro

Version

12.0v3

Operating system version

Mac OS 10.8.2

Description of the issue

When doing Insert From URL, FileMaker is returning an error 507 for some URLs.  For example, using the script step, put in this url :

https://Admin:Admin@fms12.goya.com.au/RESTfm/RESTfmSync/layout/SampleTable.RESTfm/49.simple?Field5=kwf&RFMmethod=PUTAdmin@fms12.goya.com.au/RESTfm/RESTfmSync/layout/SampleTable.RESTfm/49.simple?Field5=kwf&RFMmethod=PUT

FileMaker will not send the url and gives a 507 error.  However append a & on the end to :

https://Admin:Admin@fms12.goya.com.au/RESTfm/RESTfmSync/layout/SampleTable.RESTfm/49.simple?Field5=kwf&RFMmethod=PUT&Admin@fms12.goya.com.au/RESTfm/RESTfmSync/layout/SampleTable.RESTfm/49.simple?Field5=kwf&RFMmethod=PUT&

and it works fine.  I can't see how this is in anyway a more valid url, and the error seems to be related to field validation ( of which this field has none ) and not url validation.  However, either way it shouldn't cause this error

Steps to reproduce the problem

Create a new file with a single text field.  Add a script to do Insert From URL to the new field and use this url :

https://Admin:Admin@fms12.goya.com.au/RESTfm/RESTfmSync/layout/SampleTable.RESTfm/49.simple?Field5=kwf&RFMmethod=PUTAdmin@fms12.goya.com.au/RESTfm/RESTfmSync/layout/SampleTable.RESTfm/49.simple?Field5=kwf&RFMmethod=PUT

Run the script in the debugger, and check the last error code on that script step.

Expected result

There is no way this url should cause an error when the same url with & on the end doesn't.

Actual result

error 507.

Configuration information

NA

Workaround

Appending & can resolve it in this situation, but because you can't tell that there is anything wrong with the url in the first place, I've no idea if this issue is just related to something about the url, or if it will occur in other ways for other urls.  This leaves me no confidence in the script step and it's ability to work reliably in the future.

Outcomes