I still cannot see a reason why

Context.notFound

and

Context.notFoundHandler

would call each other. Is it really a hono thing ?

its based of the cloudflare example on the hono site https://hono.dev/getting-started/cloudflare-pages#_2-hello-world

What is this https://github.com/honojs/hono/blob/ac7eeda87f8b71843815258edf8db159c306bd2e/src/context.ts#L100

I want to see how you created the hono app

or, the "options"

exactly like their example said

import { Hono } from 'hono'
import { handle } from 'hono/cloudflare-pages'

const app = new Hono().basePath('/api')

app.get('/hello', (c) => {
  return c.json({
    message: 'Hello, Cloudflare Pages!',
  })
})

export const onRequest = handle(app)

hmm i see the example on the cloudflare site is different

import { Hono } from "hono";
const app = new Hono();

app.get("/", (ctx) => ctx.text("Hello world, this is Hono!!"));

export default app;

it does not use hono/cloudflare-pages

Say we need to find that problematic

notFoundHandler

if there is one.

Do you have a notFound(sth) call

got it

i had a

app.notFound((c) => c.notFound());

it should be

app.notFound((c) => c.text("not found", 404));

nice catch

It is

i like this edge work flow enough to figure this all out and will write a detailed how-to from dev to prod with pages+d1+queue

It is rocket science whether you like it or not.

i see the issue in the logs now

GET https://42papers.com/api/signup - Ok @ 4/28/2023, 3:37:11 p.m.
GET https://42papers.com/api/signup - Ok @ 4/28/2023, 3:38:17 p.m.
PUT https://42papers.com/api/signup - Ok @ 4/28/2023, 3:39:01 p.m.
GET https://42papers.com/api/signup - Ok @ 4/28/2023, 3:40:54 p.m.

some reason my post requests are turning into

get

.

'put

seems to be fine though

Browser side thing ?

hmm getting a 301 back for some reason

> POST /api/signup HTTP/1.1
> Host: mywebsite.com
> User-Agent: insomnia/2022.7.5
> Content-Type: application/json
> Accept: */*
> Content-Length: 57

| {
|    "firstName": "blah",
|      "email": "blah@gmail.com"
| }

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently
< Date: Fri, 28 Apr 2023 22:40:54 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Fri, 28 Apr 2023 23:40:54 GMT
< Location: https://mywebsite.com/api/signup

I would never use a 301 for post. I don't believe if it is hono.

i need to step away will dig in more later today. thanks for all the help on here really appreciate it

I would bet on it is yourself again 🙂

Are you connecting with http by any chance? You're probably just getting the normal http->https redirect

But shouldn't it still be a 307 if it is POST ?

I believe there's an option for it, but it's not the default

I want a cf console mobile app to monitor pages builds

that was it thanks