| Server IP : 66.29.132.122 / Your IP : 3.138.37.20 Web Server : LiteSpeed System : Linux business142.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64 User : admazpex ( 531) PHP Version : 7.2.34 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /proc/self/root/proc/self/root/proc/thread-self/root/proc/thread-self/root/opt/alt/ruby26/lib64/ruby/gems/2.6.0/doc/rack-3.0.8/ri/Rack/Multipart/Parser/ |
Upload File : |
U:RDoc::AnyMethod[iI"handle_fast_forward:ETI"0Rack::Multipart::Parser#handle_fast_forward;TF: privateo:RDoc::Markup::Document: @parts[o: RDoc::Markup::Paragraph; [ I"PThis handles the initial parser state. We read until we find the starting ;TI"Oboundary, then we can transition to the next state. If we find the ending ;TI"Rboundary, this is an invalid multipart upload, but keep scanning for opening ;TI"Oboundary in that case. If no boundary found, we need to keep reading data ;TI"Kand retry. It's highly unlikely the initial read will not consume the ;TI"Gboundary. The client would have to deliberately craft a response ;TI"Iwith the opening boundary beyond the buffer size for that to happen.;T: @fileI"!lib/rack/multipart/parser.rb;T:0@omit_headings_from_table_of_contents_below000[ I"();T@FI" Parser;TcRDoc::NormalClass00