sobrenome

CSS not working. And this could be an improvement for the next update! Thanks!!

Can we update to IPS 4.7.2 without issues related to CSE plugin?

Caching headers was not the issue. I found out that my domain was pointing to the ELB instead of Cloudfront.

Thanks! Has just enable it!

Your Invision Community 4 is ready The upgrade process is now complete and your Invision Community is now ready! We are currently in the process of migrating our platform from PHP7 to PHP8 in order to provide you with the greatest level of performance and security. We've identified and disabled one or more Applications or Plugins currently installed on your site which contain PHP8 incompatible code. To re-enable, you will have to upgrade to a PHP8 compatible version. Refer to the AdminCP Support page for more info. The following third party applications were disabled: bouncer

Trying to use the CSS field to customize the results, but not working. Another great feature could be adding Google option on Advanced Search. CSE is used for "all". I suggest that "all" uses IPS search and for CSE should be added another option, that should be Google. 😬

Now there is another problem. Font Awesome is not being cached by browsers. Here is my apache conf directives for fonts: # Add correct content-type for fonts AddType application/vnd.ms-fontobject .eot AddType application/x-font-ttf .ttf AddType application/x-font-opentype .otf AddType application/x-font-woff .woff AddType image/svg+xml .svg AddType application/x-font-woff2 .woff2 # Fonts ExpiresByType font/ttf "access plus 1 year" ExpiresByType font/otf "access plus 1 year" ExpiresByType font/woff "access plus 1 year" ExpiresByType font/woff2 "access plus 1 year" ExpiresByType application/font-woff "access plus 1 year" ExpiresByType application/vnd.ms-fontobject "access plus 1 year" ExpiresByType application/x-font-ttf "access plus 1 year" ExpiresByType application/x-font-opentype "access plus 1 year" ExpiresByType application/x-font-woff "access plus 1 year" ExpiresByType application/x-font-woff2 "access plus 1 year" ExpiresByType application/font-woff2 "access plus 1 year" ExpiresByType image/svg+xml "access plus 1 year"

Creating a response header policy (to overwrite origin with cache-control) will do the trick, right? Do I have to configure CORS?

I am using S3 file system for most IPS4 static content. But there is no cache-control header by default to tell browsers to cache the static content. S3 bucket has no default metadata to apply to new objects uploaded. Is there an IPS4 setting to add metadata (like "Cache-Control max-age=31536000") when we use S3 as file system?

Why don't make this HUGE improvement a core feature? @Nathan Explosion could work with IPS team! What do you think? Audio and video could be an alternative to text on the whole Community, for private message, comments, forums, etc. And would be amazing to let users get advantage of services like AWS to compress the files uploaded to certain community pattern for more compatibility and less space on disk.

The issue was on DNS. Route53 was pointing to ELB, not to Cloudfront.

Nice!!!

@Marc Stridgen could you please inform the CloudFront behavior to cache Font Awesome (Cache Policy, Origin request policy and Responde headers)?

I have tried with and without que query string. No change. The issue is related to the cookies that are sent with the request, that should not be sent. Even if I set no cookie on cache policy and no cookie on request policy, the cookies are sent. I can’t figure out why.

Yes! As long as the site written in Portuguese and many robots from UK were intensively consuming the resources, UK was blocked on Cloudfront distribution (China and Russia for the same reason). Only CSS, images and JS is hosted on S3 (using the IPS 4 feature). The website pages are on EC2, behind ELB and Cloudfront. Yes, 2 origins. One is S3 and the other one is ELB. S3 files are caching fine. The issue is related to woff2 font (that is not hosted on S3) and web manifest (also not hosted on S3).

Yes! Perfect! Thanks!

4.0.2 was approved! So Google search now can be the default search method on all community apps?

CSS, images and JS come from S3 and they hit Cloudfront cache. To make sure that I was not messing with custom policies, I have tested the manage cache policy (CachingOptimized) and no origin policy and no headers response. Same issue. The request goes along with cookies and that mess the cache.

Is it safe to use php 8.1 and IPS 4.7.1?

To make the information more complete, we can see that the font has a Cloudfront hit for IPS website: accept-ranges: bytes age: 20403 content-length: 77160 date: Tue, 16 Aug 2022 08:39:39 GMT etag: "12d68-5e5e6f965f240" last-modified: Wed, 10 Aug 2022 18:11:13 GMT server: Apache set-cookie: AWSALB=d6OLM/lKlq1X47HnfNQVg1FkXxrGusuU+o2LGV90rM4zGRFOoMpfajibPJqVNR+XboSUTzadqFbHRq21GusiocuVGg9ZKDrxKJolQWux//W99zrxDV3qxvgzl4eK; Expires=Sun, 21 Aug 2022 08:29:36 GMT; Path=/ set-cookie: AWSALBCORS=d6OLM/lKlq1X47HnfNQVg1FkXxrGusuU+o2LGV90rM4zGRFOoMpfajibPJqVNR+XboSUTzadqFbHRq21GusiocuVGg9ZKDrxKJolQWux//W99zrxDV3qxvgzl4eK; Expires=Sun, 21 Aug 2022 08:29:36 GMT; Path=/; SameSite=None via: 1.1 8bc02eb70fbe9b20b0505e49467df014.cloudfront.net (CloudFront) x-amz-cf-id: FbMiym9-hjnyPqx1kE22ga9N1Nk0EYTZpXAYtnzG8GXZ7DROZYtYeA== x-amz-cf-pop: IAD66-C2 x-cache: Hit from cloudfront x-content-type-options: nosniff :status: 200 And do not for mine: accept-ranges: bytes cache-control: max-age=2592000, public content-length: 77160 content-type: application/font-woff2 date: Tue, 16 Aug 2022 14:33:40 GMT etag: "12d68-5e3c8209e1ce0" expires: Thu, 15 Sep 2022 14:33:40 GMT last-modified: Thu, 14 Jul 2022 18:32:43 GMT server: Apache/2.4.54 (Ubuntu) set-cookie: AWSALB=ldcCFgF+iJ0E/9dkC7wI4cjnuEVQbpZIdhNTudEvrd2RNGyXq1KOUVxtocvI6fgV6ZgUUbC34vikqmDhDGNxJuswDudtAo0P8RpZDyi/k2/Njzu5uQUSS0REf8QM; Expires=Tue, 23 Aug 2022 14:33:40 GMT; Path=/ set-cookie: AWSALBCORS=ldcCFgF+iJ0E/9dkC7wI4cjnuEVQbpZIdhNTudEvrd2RNGyXq1KOUVxtocvI6fgV6ZgUUbC34vikqmDhDGNxJuswDudtAo0P8RpZDyi/k2/Njzu5uQUSS0REf8QM; Expires=Tue, 23 Aug 2022 14:33:40 GMT; Path=/; SameSite=None; Secure :status: 200 On the response, the difference is huge. How can I configure Cloudfront to achieve the same request and response?

I can't hit Cloudfront cache for font awesome. I have checked that IPS can serve font awesome from Cloudfront. Here is my request (https://www.webpagetest.org/result/220816_BiDcWR_ACG/1/details/#waterfall_view_step1😞 :authority: fisiculturismo.com.br :method: GET :path: /applications/core/interface/font/fontawesome-webfont.woff2?v=4.7.0 :scheme: https accept: */* accept-encoding: gzip, deflate, br accept-language: en-US,en;q=0.9 cookie: AWSALB=V+qLZCNbjEfbsPzZCvXjy8lR1d7lJw+6Qz1bNnwYg3ri9BdDQEtMndfBsf/Hz6jHSj9ffTMEA4MsyUU2es6+KXvX4j590g0Rnn2XevQuROzwR/vyxmaPt32qn142; AWSALBCORS=V+qLZCNbjEfbsPzZCvXjy8lR1d7lJw+6Qz1bNnwYg3ri9BdDQEtMndfBsf/Hz6jHSj9ffTMEA4MsyUU2es6+KXvX4j590g0Rnn2XevQuROzwR/vyxmaPt32qn142; ips4_IPSSessionFront=fi6hu5jv1pl00tp6jshi3uf2ka origin: https://fisiculturismo.com.br referer: https://fisiculturismo.com.br/ sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="104", "Google Chrome";v="104" sec-ch-ua-mobile: ?1 sec-ch-ua-platform: "Android" sec-fetch-dest: font sec-fetch-mode: cors sec-fetch-site: same-origin user-agent: Mozilla/5.0 (Linux; Android 8.1.0; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.79 Mobile Safari/537.36 PTST/220727.131331 customize waterfall • View all Images • View HTTP/2 Dependency Graph • Filmstrip Connection View Here is IPS website request (https://www.webpagetest.org/result/220816_BiDcMK_A8Y/2/details/#waterfall_view_step1😞 :authority: invisioncommunity.com :method: GET :path: /applications/core/interface/font/fontawesome-webfont.woff2?v=4.7.0 :scheme: https accept: */* accept-encoding: gzip, deflate, br accept-language: en-US,en;q=0.9 origin: https://invisioncommunity.com referer: https://invisioncommunity.com/forums/ sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="104", "Google Chrome";v="104" sec-ch-ua-mobile: ?1 sec-ch-ua-platform: "Android" sec-fetch-dest: font sec-fetch-mode: cors sec-fetch-site: same-origin user-agent: Mozilla/5.0 (Linux; Android 8.1.0; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.79 Mobile Safari/537.36 PTST/220727.131331 My request sends the loud balancer sticky cookies and ips4 session cookie (AWSALB, AWSALBCORS, ips4_IPSSessionFront). On Cloudfront I am using an origin request policy with no cookie. What am I missing?

Amazing! Thanks @DawPi!

Is it possible to remove some Pages databases from the search index?

This feature is essencial. Most users will not change the default search. I will wait this feature to install the plugin. 🙏🏻