te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>next.js - NextJS 14, SSR and CloudFront caching initial empty searchParams - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>next.js - NextJS 14, SSR and CloudFront caching initial empty searchParams - Stack Overflow

    next.js - NextJS 14, SSR and CloudFront caching initial empty searchParams - Stack Overflow

    programmeradmin2浏览0评论

    I am attempting to get a NextJS 14 SSR app to work with cloudfront. The initial load uses searchParams which are always empty. So CloudFront caches the empty response.

    Here is the SAM template section for CF

    NextDistribution:
    Type: AWS::CloudFront::Distribution
    Properties:
      DistributionConfig:
        Origins:
          - Id: nextS3Origin
            DomainName: !GetAtt NextBucket.RegionalDomainName
            OriginAccessControlId: !Ref NextOriginAccessControl
            S3OriginConfig: {} # Required, but empty for OAC
          - Id: nextAPIGatewayOrigin
            DomainName: !Sub '${ServerlessHttpApi}.execute-api.${AWS::Region}.amazonaws'
            CustomOriginConfig:
              HTTPSPort: '443'
              OriginProtocolPolicy: https-only
        Enabled: 'true'
        Comment: 'Next.js Distribution'
        HttpVersion: http2

        DefaultRootObject: ''
        DefaultCacheBehavior:
          TargetOriginId: nextAPIGatewayOrigin
          CachePolicyId: 4135ea2d-6df8-44a3-9df3-4b5a84be39ad
          ForwardedValues:
            QueryString: 'true'
            Cookies:
              Forward: all
          Compress: 'true'
          AllowedMethods:
            - DELETE
            - GET
            - HEAD
            - OPTIONS
            - PATCH
            - POST
            - PUT
          ViewerProtocolPolicy: redirect-to-https
          MaxTTL: '31536000'
        CacheBehaviors:
          - PathPattern: '/_next/static/*'
            TargetOriginId: nextS3Origin
            CachePolicyId: 658327ea-f89d-4fab-a63d-7e88639e58f6
            AllowedMethods:
              - GET
              - HEAD
            ForwardedValues:
              QueryString: 'false'
              Cookies:
                Forward: none
            Compress: 'true'
            ViewerProtocolPolicy: https-only
          - PathPattern: '/static/*'
            TargetOriginId: nextS3Origin
            CachePolicyId: 658327ea-f89d-4fab-a63d-7e88639e58f6
            AllowedMethods:
              - GET
              - HEAD
            ForwardedValues:
              QueryString: 'false'
              Cookies:
                Forward: none
            Compress: 'true'
            ViewerProtocolPolicy: https-only
        PriceClass: PriceClass_100
        ViewerCertificate:
          CloudFrontDefaultCertificate: 'true'

    And my index page:

    export default async function Page({
  searchParams
}: {
  searchParams: Promise<{ [key: string]: string | string[] | undefined }>
}) {
  const pa{  itemId } = await searchParams
  
  return (
    <>
      {!itemId ? 'loading' : null}
      
    </>
  )
}

    Works fine in direct access mode (I am using the lambda web adapter). I can of course go client side but thats not the goal.

    See anything amiss here? How can I prevent CF from caching this till the query params get recognized. Not totally sure why they are not initially. The request is simply foo?itemId=122

    I think part of the issue is the new async searchParams which renders before the query params actually are there. My thoughts around fixing this is to be able to invalidate/disable cache if itemId doesnt exist but have not found a solution.

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论