Closed Bug 73231 Opened 23 years ago Closed 23 years ago

nsFileTransport should report progress even if content-length is unknown

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla0.9

People

(Reporter: darin.moz, Assigned: darin.moz)

Details

Attachments

(1 file)

fixes the problem
4.00 KB, patch
Details | Diff | Splinter Review 
nsFileTransport should report progress even if content-length is unknown (a la 
nsSocketTransport).
Blocks: 64833
Keywords: mozilla0.9
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Keywords: nsbeta1

    
    

    
  
dougt, rpotts: can you guys review this patch?  thx!

    
  
Keywords: patch

    
    

    
  
how can the content length be unknown?

    
    

    
  
the mStreamIO object can return -1 for the content length, which might
correspond to a stream being downloaded, for example, and then pumped
through a file transport.  consider that embedders might be getting 
data from outside sources.

    
    

    
  
roger that. sr=

    
    

    
  
Looks good.  r/sr=rpotts

-- rick


    
    

    
  
fix checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED

    
  
Component: Networking: File → Networking
QA Contact: tever → bbaetz

    
    

    
  
VERIFIED checked in via lxr.
Status: RESOLVED → VERIFIED

    
  
No longer blocks: 64833

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: