search

bkper / bkper-issues

Feature requests and enhancements to existing bkper modules can also be filed here.
https://bkper.com/
2 stars 0 forks source link

unusual behaviour when attaching a not supported file #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Attach anyname.json file in a transaction

What is the expected output? What do you see instead?
I would expect one of two possible responses:
  - Success: file accepted
  - Fail: file not supported

I got a weird error: Only image files are supported, 

Strangely a file name pointing to C:\fakepath\items.json seems to be attached,
but I have no idea what you mean by C:\fakepath 

;-)

I´m using G Chrome 44

Original issue reported on code.google.com by ma...@zoqui.com on 23 Jul 2015 at 10:01

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by ma...@zoqui.com on 23 Jul 2015 at 10:08

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi Marco,

Many thanks for reporting!

Actually, this fakepath is a security standard from chrome, take a look:

http://stackoverflow.com/questions/18254118/fakepath-issue-in-chrome-browser

What is really not correct is that the path of file invalid file should not be 
appearing as it was uploaded! We will fix this.

Cheers

Original comment by m...@nimbustecnologia.com.br on 24 Jul 2015 at 1:05