Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

'application/pdf' mime type recognized as a page #1014

Closed
LavrovArtem opened this issue Jan 17, 2017 · 1 comment
Closed

'application/pdf' mime type recognized as a page #1014

LavrovArtem opened this issue Jan 17, 2017 · 1 comment
Assignees
@LavrovArtem
Labels
AREA: server STATE: Auto-locked Issues that were automatically locked by the Lock bot SYSTEM: resource processing TYPE: bug
Milestone
Sprint #3

Comments

@LavrovArtem
Copy link
Contributor

A browser sends the accept header with the page mime type when I click on a link. For example:
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
But we don't consider the content-type header from response. We process resource like a page if the content-type header equals application/pdf or text/plain etc.
See DevExpress/testcafe#1130
@LavrovArtem LavrovArtem added this to the Sprint #3 milestone Jan 17, 2017
@LavrovArtem LavrovArtem self-assigned this Jan 17, 2017
LavrovArtem added a commit to LavrovArtem/testcafe-hammerhead that referenced this issue Jan 17, 2017
@LavrovArtem
Fix The page resource detecting works incorrectly (close DevExpress…
fd67584 
…#1014)
@churkin churkin changed the title The page resource detecting works incorrectly 'application/pdf' mime type recognized as a page Jan 19, 2017
@AlexanderMoskovkin AlexanderMoskovkin mentioned this issue Jan 19, 2017
Merged
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
@LavrovArtem @AndreyBelym
Fix The page resource detecting works incorrectly (close DevExpress…
bba4688 
…#1014) (DevExpress#1015)
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@LavrovArtem LavrovArtem

Labels
AREA: server STATE: Auto-locked Issues that were automatically locked by the Lock bot SYSTEM: resource processing TYPE: bug
Projects
None yet
Milestone
Sprint #3
Development

No branches or pull requests
1 participant
@LavrovArtem