[Looking for Charlie's main web site?]

Join me and Mikey on a Youtube Live FusionReactor 8.3 webinar, Feb 11 at 2p US Eastern

Come learn what's new about FusionReactor 8.3 in the first of what are planned to be a series of Youtube Live webinars from the folks behind FusionReactor. In this first episode, FR Technical Support Engineer Michael (Mikey) Flewitt and I will be teaming up to introduce FusionReactor 8.3.0, which should be released very soon.

Join us on Feb 3 at 2p US EST (and set a reminder/subscribe) here: https://www.youtube.com/watch?v=f0TKfnhIE24

Besides discussing and demonstrating what's new in the 8.3.0 release (which includes several features), we will of course be open to your questions. That's the whole point of going to the Youtube Live format!

What to expect in future episodes

And again, this is the first of what are planned to be a series, with future episodes addressing not only FR feature changes but reviewing FR features you might have missed, and as important: how to use FR to solve important problems in CF, Lucee, and Java servers. We're also open to addressing broader issues related to such technologies, in an "ask me anything" format.

So come along, and do subscribe, and bring your questions and comments. We're trying to make it a resource that will benefit many. Of course, it's our first, so we will iron out the kinks as we go!

How to solve failing "api" URLs, in CF2016 and 11 (not a problem in CF2018)

If you're trying to run a request against CF 2016 (or perhaps 11), and the URL you're using has a path which starts with /api, you may find that the request fails to run (it may give a blank page). What gives? (It was related to the CF2016 API Manager, not CF's REST services feature.)

And what can you do about it, if you are on CF2016 or 11, and you want to use /api for your URLs? There are are two choices, depending on your needs: in brief, you can either:

  • change your /api folder to a new name (which I realize may not appeal to all to some)
  • or change the CF configuration, to STOP it treating /api specially for the API Manager's use. You would do this by editing two CF config files, urlworkermap.properties and web.xml (but this will break the ability of the API Manager to introspect REST services in CF2016 or CF11, though not CF2018)

TLDR; if you're bold and a risk taker, you can jump to the bottom to see my list of changes to make for that second option. As is often the case, there is risk in making changes in a cavalier fashion. There are various things to consider, and I warn of them below--but the good news is that this is a change that may take only minutes to do, once you've been careful to read about how to do it effectively.

Read on for more, including pros and cons of each choice, what to change and where, why this problem NO LONGER happens from CF2018 onward, and more.

(And if you are not familiar with the CF Enterprise API Manager, which is installed separately from CF, you can read about it here.)

[....Continue Reading....]

Copyright ©2020 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting