[Bug 2068529] Re: Focal: Reverse proxy POST with with body length >1000 is missing body
Thanks for the note Mauricio.
The bug is not present in Jammy.
I've edited the bug description to include a reproducer that reflects
the message length limit.
** Description changed:
POST requests to an apache2 server with the below configuration do not
- forward the message body.
+ forward the message body if it is larger than 1024 bytes.
Affected versions:
apache2 2.4.41-4ubuntu3.17 in focal
Steps to reproduce:
sudo apt-get install apache2
sudo a2enmod proxy
sudo a2enmod proxy_http
Add /etc/apache2/sites-enabled/test_proxy.conf
```
Listen 9443
- ServerName focal.cld.lan
+ ServerName focal.cld.lan
- ProxyRequests Off
- ProxyPass "/" "http://127.0.0.1:8899/;
- ProxyPassReverse "/" "http://127.0.0.1:8899/;
+ ProxyRequests Off
+ ProxyPass "/" "http://127.0.0.1:8899/;
+ ProxyPassReverse "/" "http://127.0.0.1:8899/;
- ErrorLog ${APACHE_LOG_DIR}/testproxy-error.log
- CustomLog ${APACHE_LOG_DIR}/testproxy-access.log combined
+ ErrorLog ${APACHE_LOG_DIR}/testproxy-error.log
+ CustomLog ${APACHE_LOG_DIR}/testproxy-access.log combined
```
sudo systemctl restart apache2
nc -k -l 8899
wget http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/InRelease
curl -d "@InRelease" -H "Content-type: text/plain" -X POST
http://127.0.0.1:9443/
Curl hangs for a while until the request times out.
+
+ EDIT: The first curl here succeeds, the second does not:
+
+ DATA=`tr -dc A-Za-z0-9 http://127.0.0.1:9443 -vvv
+
+ DATA=`tr -dc A-Za-z0-9 http://127.0.0.1:9443 -vvv
** Summary changed:
- Focal: Reverse proxy POST with with body length >1000 is missing body
+ Focal: Reverse proxy POST with with body length >1024 is missing body
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068529
Title:
Focal: Reverse proxy POST with with body length >1024 is missing body
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2068529/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068529] [NEW] Focal: Reverse proxy POST with with body length >1000 is missing body
Public bug reported:
POST requests to an apache2 server with the below configuration do not
forward the message body.
Affected versions:
apache2 2.4.41-4ubuntu3.17 in focal
Steps to reproduce:
sudo apt-get install apache2
sudo a2enmod proxy
sudo a2enmod proxy_http
Add /etc/apache2/sites-enabled/test_proxy.conf
```
Listen 9443
ServerName focal.cld.lan
ProxyRequests Off
ProxyPass "/" "http://127.0.0.1:8899/;
ProxyPassReverse "/" "http://127.0.0.1:8899/;
ErrorLog ${APACHE_LOG_DIR}/testproxy-error.log
CustomLog ${APACHE_LOG_DIR}/testproxy-access.log combined
```
sudo systemctl restart apache2
nc -k -l 8899
wget http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/InRelease
curl -d "@InRelease" -H "Content-type: text/plain" -X POST
http://127.0.0.1:9443/
Curl hangs for a while until the request times out.
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068529
Title:
Focal: Reverse proxy POST with with body length >1000 is missing body
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2068529/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064717] Re: ceph-volume needs "packaging" module
This also affects ceph-volume 19.2.0~git20240301.4c76c50-0ubuntu6 in Noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064717 Title: ceph-volume needs "packaging" module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2064717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064176] Re: LXD fan bridge causes blocked tasks
** Attachment added: "apport.linux-image-6.5.0-28-generic._9l2i4n1.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+attachment/5772647/+files/apport.linux-image-6.5.0-28-generic._9l2i4n1.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064176 Title: LXD fan bridge causes blocked tasks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064176] [NEW] LXD fan bridge causes blocked tasks
Public bug reported: Hi, cross posting this from https://github.com/canonical/lxd/issues/12161 I've got a lxd cluster running across 3 VMs using the fan bridge. I'm using a dev revision of LXD based on 6413a948. Creating a container causes the trace in the attached syslog snippet; this causes the container creation process to hang indefinitely. ssh logins, `lxc shell cluster1`, and `ps -aux` also hang. Apr 29 17:15:01 cluster1 kernel: [ 161.250951] [ cut here ] Apr 29 17:15:01 cluster1 kernel: [ 161.250957] Voluntary context switch within RCU read-side critical section! Apr 29 17:15:01 cluster1 kernel: [ 161.250990] WARNING: CPU: 2 PID: 510 at kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0 Apr 29 17:15:01 cluster1 kernel: [ 161.251003] Modules linked in: nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan ip6_udp_tunnel udp_tunnel dummy br idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common kvm_intel kvm irqbypass crct10dif _pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel vmw_vsock_virtio_transport 9pnet_virtio xhci_ pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd lpc_ich virtiofs i2c_smbus vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua grace sch_fq_codel drm sunrpc efi_pstore virtio_rng ip_tables x_tables autofs4 Apr 29 17:15:01 cluster1 kernel: [ 161.251085] CPU: 2 PID: 510 Comm: nmbd Tainted: P O 6.5.0-28-generic #29~22.04.1-Ubuntu Apr 29 17:15:01 cluster1 kernel: [ 161.251089] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022 Apr 29 17:15:01 cluster1 kernel: [ 161.251091] RIP: 0010:rcu_note_context_switch+0x2a7/0x2f0 Apr 29 17:15:01 cluster1 kernel: [ 161.251095] Code: 08 f0 83 44 24 fc 00 48 89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 40 02 01 e8 79 b2 f2 ff <0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c Apr 29 17:15:01 cluster1 kernel: [ 161.251098] RSP: 0018:b9cbc11dbbc8 EFLAGS: 00010046 Apr 29 17:15:01 cluster1 kernel: [ 161.251101] RAX: RBX: 941ef7cb3f80 RCX: Apr 29 17:15:01 cluster1 kernel: [ 161.251103] RDX: RSI: RDI: Apr 29 17:15:01 cluster1 kernel: [ 161.251104] RBP: b9cbc11dbbe8 R08: R09: Apr 29 17:15:01 cluster1 kernel: [ 161.251106] R10: R11: R12: Apr 29 17:15:01 cluster1 kernel: [ 161.25] R13: 941d893e9980 R14: R15: 941d80ad7a80 Apr 29 17:15:01 cluster1 kernel: [ 161.251113] FS: 7c7dcbdb8a00() GS:941ef7c8() knlGS: Apr 29 17:15:01 cluster1 kernel: [ 161.251115] CS: 0010 DS: ES: CR0: 80050033 Apr 29 17:15:01 cluster1 kernel: [ 161.251117] CR2: 5a30877ae488 CR3: 000105888003 CR4: 00170ee0 Apr 29 17:15:01 cluster1 kernel: [ 161.251122] Call Trace: Apr 29 17:15:01 cluster1 kernel: [ 161.251128] Apr 29 17:15:01 cluster1 kernel: [ 161.251133] ? show_regs+0x6d/0x80 Apr 29 17:15:01 cluster1 kernel: [ 161.251145] ? __warn+0x89/0x160 Apr 29 17:15:01 cluster1 kernel: [ 161.251152] ? rcu_note_context_switch+0x2a7/0x2f0 Apr 29 17:15:01 cluster1 kernel: [ 161.251155] ? report_bug+0x17e/0x1b0 Apr 29 17:15:01 cluster1 kernel: [ 161.251172] ? handle_bug+0x46/0x90 Apr 29 17:15:01 cluster1 kernel: [ 161.251187] ? exc_invalid_op+0x18/0x80 Apr 29 17:15:01 cluster1 kernel: [ 161.251190] ? asm_exc_invalid_op+0x1b/0x20 Apr 29 17:15:01 cluster1 kernel: [ 161.251202] ? rcu_note_context_switch+0x2a7/0x2f0 Apr 29 17:15:01 cluster1 kernel: [ 161.251205] ? rcu_note_context_switch+0x2a7/0x2f0 Apr 29 17:15:01 cluster1 kernel: [ 161.251208] __schedule+0xcc/0x750 Apr 29 17:15:01 cluster1 kernel: [ 161.251218] schedule+0x63/0x110 Apr 29 17:15:01 cluster1 kernel: [ 161.251222] schedule_hrtimeout_range_clock+0xbc/0x130 Apr 29 17:15:01 cluster1 kernel: [ 161.251238] ? __pfx_hrtimer_wakeup+0x10/0x10 Apr 29 17:15:01 cluster1 kernel: [ 161.251245] schedule_hrtimeout_range+0x13/0x30 Apr 29 17:15:01 cluster1 kernel: [ 161.251248] ep_poll+0x33f/0x390 Apr 29 17:15:01 cluster1 kernel: [ 161.251254] ? __pfx_ep_autoremove_wake_function+0x10/0x10 Apr 29 17:15:01 cluster1 kernel: [ 161.251257] do_epoll_wait+0xdb/0x100 Apr 29 17:15:01 cluster1 kernel: [ 161.251259] __x64_sys_epoll_wait+0x6f/0x110 Apr 29 17:15:01 cluster1 kernel: [ 161.251265] do_syscall_64+0x5b/0x90 Apr 29 17:15:01 cluster1 kernel: [ 161.251270] ?
