- imgix now returns a “403 Forbidden” error on signed images with an invalid
sparameter instead of a “401 Unauthorized” error. Still a 4xx error, but more correct.
When you’re looking for information about an imgix feature, the API documentation is your friend—every parameter in the service is listed with examples, ranges, and default values. We also have in-depth tutorials for more complex multi-parameter use cases.
This is great for humans who need to know the ins and outs of imgix, but what about machines? If you’re building tools, libraries, or URL generators based on our Image URL API, having a single, machine-readable source of truth about the capabilities of all available parameters is crucial. Fortunately, it’s available on GitHub in JSON format and as Bower and NPM packages.
- Added account type and optional features list to the account view
- Upgraded the source “default parameters” field to check parameter values for validity, instead of just parameter names
- Also, updated the list of legal parameter names to include some newer additions
- Added validation to prevent user names from containing brackets
- Released support for HTTP/2
HTTP/2 is a big leap forward for websites and web apps. It improves performance by making resource requests more efficient, which means that your pages should load much faster—with a particular boost for image-heavy sites.
imgix is always working to squeeze the most performance out of your images, so we’re pleased to announce that we now offer HTTP/2 free of charge to all accounts.
What You Should Know
- HTTP/2 is on automatically for all accounts, and will be the default connection method over secure (HTTPS) connections. You don’t need to change your account or Sources to use it and there is no additional cost.
- HTTP/2 fixes many of the shortcomings found in HTTP/1.1, so you no longer need to use workarounds such as Source sharding or image sprites to get maximum performance. If you’re using these techniques, you should consider discontinuing them. They can sometimes hurt performance under HTTP/2 due to differences in the way it requests resources like images.
- Added a note to the Managing User-Generated Images tutorial to clarify caching behavior when testing newly-uploaded images.