I'm using openserver and encountered a problem while trying to test htmx on my local server and understand it - I've noticed the PUT method is mainly used, and this turned out to be a problem, since I could not get openserver to work with this method, it is disabled in openserver, and setting up apache files did not lead to anything, I also think this can be a problem for real servers where this method is not enabled... any thoughts on that.

Htmx uses the http method you tell it to use.

hx-post

issues a post request,

hx-put

issues a put request. If you want to use a server that doesn't handle put requests, don't use put requests.

Yes, thanks. I've run a couple quick tests, but don't see anything obvious. I have to run out right now, but will look at this more this afternoon.

@tall-dinner-62086 - yes I have noticed this, but I was doing a tutorial, and I got stuck middle of it on the put method.

Which tutorial?

I find it hard to believe that any web server would just not work with PUT requests, they're a basic part of the HTTP standard.

I am personally of the opinion that server configuration is outside the scope of the htmx documentation, and find it fairly obvious that if you're using a specific http method, you need to know what that means and whether or not your web server supports it. Do other frontend frameworks mention this sort of thing in their documentation? I don't know what openserver is, but if it doesn't even implement/allow all the HTTP verbs, can it really be called a web server? I also don't think an example would qualify as a "tutorial" as you called it, but that might be a bit nitpicky of me. That said, I would not necessarily be angry about a note in the docs along the lines of "Make sure your web server supports a specific http verb before using it", probably somewhere around here?

I know of servers in production on campuses that disallow anything but GET and HEAD. you should always know what your server allows.

pack it up boys

LMAO

but also

i got excited that spas were finally on the defensive

\> mfw last ten years as the SPA rolled through web dev

I'm so sorry you're having trouble with this. I've dug into it more, and it looks like the WS extension is calling one of the internal htmx APIs incorrectly. It's a tiny change to the extension code, and I've just posted it to DEV. You should be able to see this work correctly, now, if you use the latest version on DEV.

Thanks @gorgeous-ghost-95789 ! Tagging @mysterious-tomato-195 to see this as well. (My example was just a minimal one to help them out) I’m sticking with polling for now 😀

thank you for digging in ben!

Re: Polling:

One day I will try https://arc.codes/ and then the websockets will be unleashed!

I have the following html:

<button hx-swap="outerHTML" hx-post="/expire" value="4823">
      Expire
   </button>

It issues a request as expected, hits my backend, but contains no payload: body/params/query all empty. The "parameters" docs say "By default, an element that causes a request will include its value if it has one.". Am I missing something?

Thanks!

Can someone explain please how

hx-trigger

's "intersect once/root/threshold" events are working? Because I have difficulties making sense of the documentation on this topic. Does anyone have an example?

I'm still having issues. It seems like it works fine when I follow the example closely, but it reverts to that bugged behaviour once the

<form ws-send><input name=chat_message></form>

is inserted dinamycally by htmx

Another thing, which is probably not a real issue: when there are multiple inputs with the same name inside of the

<form ws-send>

nothing happens when submitting them

I have solved this by having a "static"

<form ws-send>

and just updating the inputs, but maybe it's useful to know if this is not the intended behaviour

Does htmx support dynamically adding styles based on a response? Lookng at my base CSS of 200kb, I'm thinking I would like to break it up a bit...

You can put a

<link rel=stylesheet>

in your response.

Does HTMX do anything to not add stylesheets it has already added? Or we would just rely on the browser recognizing that the stylesheet has already been referenced so it doesn't re-request it?