https://htmx.org logo
Powered by
# htmx-general
  • m
    This is as a post?
  • m
    It should be included in the body
  • b
    yes I am trying exactly to do that
  • b
    if I turn the nginx header size big enough (like on my testing system) everything works out - thats why I did not see it until some user tried it with a too big image
  • b
    can you tell me why the header is extended after the 
    page
    -variable?
  • m
    🤔
  • m
    it's showing up in the headers?
  • m
    that doesn't make any sense
  • m
    can you show me a screen shot of the headers?
  • m
    I wonder if that's the CURRENT_URL
  • g
    looks like search params, not headers
  • m
    yeah, that's sus
  • b
    you are absolutely right, I meant the "headers" tab of webdev, my bad
  • b
    so what did I do wrong?
  • m
    I don't see anything wrong. It may be that the query params were too long for your nginx setup (but work fine locally)
  • m
    It's a GET so parameters will be passed as query parameters
  • m
    you could flip to a POST or whatever and they will go up in the body
  • m
    and then you won't run into query string limitations
  • b
    so the thing is .. usually I have three buttons there: save, delete, abort
  • b
    save is obviously a post
  • b
    but delete and abort are just gets
  • m
    can you make 
    delete
    a real 
    DELETE
    ?
  • m
    and then on the get for abort, can you use 
    hx-include="unset"
  • m
    I think you don't want to include all that junk on the GET for the abort
  • b
    also not in the delete 🙂
  • b
    so i would have a 
    hx-include="...."
    in the parent, and then in some child I have a 
    hx-include="unset"
    and this will work?
  • b
    then I could just stick with the GET right?
  • b
    so: save -> hx-include on everything, POST delete -> hx-include on everything, but hx-include="unset" on the button -> GET abort -> hx-include on everything, but hx-include="unset" on the button -> GET
  • b
    the delete is a get, because it leads to a page where info is posted first and a confirmation is shown
  • b
    no i definitely did not want that.
1...633634635...1146Latest