cfc | Copy files | iOS library

The quick and dirty is that you should be using role based permissions. If you load the user's roles on login, you should be able to check if the user has a specific role before accessing various functionality throughout the application.

Let's say you have a basic app like this:

When a form is posted to a CFML server, the posted file is saved in a temporary directory before any of your code runs. All does is to copy a file from that temporary directory to the location you want it to be. Your remote server ServerB has no idea about any file posted on ServerA, so will not help you.

The action is misleading. It's not upload-ing anything. It's just copying from a predetermined temp directory. The web server handles the uploading before the CF server is even involved.

You will likely need to on ServerA to a specific place, and then it needs to post that file to your web service on ServerB. Then ServerB should be able to use to transfer it from the upload temp directory to wherever you need it to be. That said I have never tried this when posting to a web service.

Alternatively you could just post the file directly to ServerB in the first place, to save needing ServerA to be an intermediary. This might not be possible, of course.

Because I already gave you a solution within my comments, I’m posting it as an answer here, so that others with similar issues may find the root of their charset issues.

The issue described above is very often the result of conflicting charset encodings. For example, if you are reading an ISO-8859-1 encoded file and outputting it with UTF8 without having them converted (de-/encoded) properly.

For the purpose of sending characters through a webapp as you are doing, the most common charset encoding as of today is UTF-8.

All you need to do is to harmonize characterset encodings or at least ensure that the encodings are set in such a manner that the processing engine is able to encode and decode the charsets correctly. What you can do in your case is:

1. Verify the encoding of the template .cfm file and make sure it’s saved as UTF-8
2. Define UTF-8 as your web charset in Lucee Administrator » Settings » Charset » Web charset
3. Define UTF-8 as your ressource charset in Lucee Administrator » Settings » Charset » Resource charset.
4. Make sure there are no other places where charset encodings are incorrectly set, such as a http server response header of “content-type: text/html;charset...” or a html meta-tag with a charset directive.
5. If you have other type of ressources, such as a database, then you may need to check those also (connection and database/table settings).

Note: That charset doesn’t always have to be UTF-8 (UTF-8 might use multiple bytes for certain characters). There may be use cases you would achieve the same result with single byte encodings, such as ISO-8559-1, that would also need less computing ressources and less payload.

I hope this may help others with similar issues.

OK following from Redtopia's comment, I created this:

The problem is that the hasPrice property has type="binary". In ColdFusion, true/false properties should have type="boolean"

I think it's like Sergey mentioned.

Twincat will remember the latest selected language.

I think it is bound to the latest selected language within the specific project.

This is how I passed the values to the API. Again, just passing along code that worked, not saying this is the only way

Your first issue will be that returntype="JSON" - it looks like you're confusing returntype and returnformat. There are various ways of achieving what you're trying to do, eg each of these would return the same result:

What version of FW/1 are you using? I assume the latest?

I know nothing about how Framework7's ajax features work, but I would try setting preflightOptions = true, if you haven't already, in your FW/1 framework settings in Application.cfc and see if that remedies your issue.

Check out the OPTIONS Support section of http://framework-one.github.io/documentation/4.3/developing-applications/#options-support

UPDATE

Since preFlightOptions is being used...

My next suggestion is to set your allowed headers in the FW/1's framework settings. You can do this by defining optionsAccessControl.headers = "your, headers, here". This is all mentioned in the link I already shared.

You can define the optionsAccessControl struct as a whole if you'd like and set the other keys as well.