Page History
| Table of Contents |
|---|
4.0.5
More Logging TLC
The more logging gets used the more ways we see how this can be improved. Here is a summary of what we've added:
- To help speed up the population of the HTTP Logs utility, special log index files are automatically created. These files contain all of the data needed for the form and do not replace the individual log files. You can rebuild your log indexes at anytime.
- The HTTP Logs utility has a new column which displays the Remote Address (for requests) and the Execute Time (for responses).
- Searching logs no longer shrinks the list in the HTTP Logs utility but finds the next log matching the search criteria. Users can go forwards and backwards via newly added VCR style Find Next and Find Previous buttons.
- Logs for a specified date can now be archived via the Archive Logs menu. This feature zips up your logs and stores them in the archive sub-folder.
Image Automation
You might have already noticed that setting the Response body will often automatically set the Content-Type header field to the correct value (e.g., application/xml, application/json, text/html, etc.). This exists as a safety check for when developers forget to specify this. We've updated this feature to properly identify PNG, JPG, and GIF data formats.
Here's a Wild Idea...
- Non-Authenticated URLs now support wildcards:
In the above example, an API developer can now support multiple OAuth redirect URLs (e.g., /oauth/google, /oauth/facebook, /oauth/microsoft, etc.) without having to list each one individually. - Whitelisted IPs also support wildcards:
In the above example, an API developer can now support a range of IPs rather than having to list each one individually.
It's a Bug Hunt
As always, we continue to squash bugs that come up in real world scenarios. Private William Hudson would have been proud.
4.0.4
Breaking the Log Jam
In our last release we added a feature so that individual endpoints can be excluded from logging. Still, the number of log files that get generated can still be daunting and difficult to sift through when specific issues need to be investigated. Never fear...the new HTTP Logs utility is here! Just launch the NDW_HTTP_LOGS form, confirm the log directory, and wonder why we never created this sooner!
...
