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

Lack of User-Agent header causing 403 on some servers #167

Closed
getodk-bot opened this issue Sep 5, 2016 · 2 comments
Closed

Lack of User-Agent header causing 403 on some servers #167

getodk-bot opened this issue Sep 5, 2016 · 2 comments
Assignees
@mitchellsundt
Labels
bug good first issue Good for newcomers! Experienced ODK devs, only take these if they need to be fixed quickly. =) help wanted Issues that are well-specified and don't require too much context.
Milestone
April 2017

Comments

@getodk-bot
Copy link
Member

Issue by mitchellsundt
Thursday Jul 09, 2015 at 19:45 GMT
Originally opened as getodk/getodk#1123 (0 comment(s))

Originally reported on Google Code with ID 1122

When ODK Collect interacts with some hosting services, they expect and require a User-Agent
header.

This causes a 403 to be returned.

Would be desirable for ODK Collect to send a bogus User-Agent header to appease these
finicky servers.

Reported by mitchellsundt on 2015-03-25 01:02:55
@mitchellsundt mitchellsundt mentioned this issue Sep 5, 2016
Closed
@yanokwa yanokwa removed the Collect label Sep 16, 2016
@yanokwa yanokwa added help wanted Issues that are well-specified and don't require too much context. good first issue Good for newcomers! Experienced ODK devs, only take these if they need to be fixed quickly. =) bug and removed medium priority enhancement labels Nov 3, 2016
@greg-mogavero
Copy link

I can try tackling this. Does anyone have an example of a host that returns the 403 so I can reproduce the bug?

@lognaturel
Copy link
Member

@vgmd Apologies for not responding to your question! Please find us in Slack here if ever you need more answers.

In the mean time, @alxndrsn has expressed interest in addressing this.

alxndrsn added a commit to alxndrsn/collect that referenced this issue Mar 30, 2017
@alxndrsn
Include User-Agent header in HTTP requests
b9b4f1c 
Closes getodk#167
@alxndrsn alxndrsn mentioned this issue Mar 30, 2017
Merged
lognaturel pushed a commit that referenced this issue Mar 31, 2017
@alxndrsn @lognaturel
Include User-Agent header in HTTP requests (#800)
74ad193 
Closes #167
@alxndrsn alxndrsn mentioned this issue Apr 3, 2017
Closed
alxndrsn added a commit to medic/medic-collect that referenced this issue Apr 3, 2017
@alxndrsn
Set User-Agent header when making HTTP requests
4db697a 
Backported from upstream: getodk/collect#167

Issue: medic/cht-core#3334
@alxndrsn alxndrsn mentioned this issue Apr 3, 2017
Merged
alxndrsn added a commit to medic/medic-collect that referenced this issue Apr 4, 2017
@alxndrsn
Set User-Agent header when making HTTP requests
a13696b 
Backported from upstream: getodk/collect#167

Issue: medic/cht-core#3334
@lognaturel lognaturel added this to the April 2017 milestone May 2, 2017
snavarreteimmap pushed a commit to snavarreteimmap/collect that referenced this issue Oct 2, 2020
@alxndrsn @lognaturel
Include User-Agent header in HTTP requests (getodk#800)
5aff853 
Closes getodk#167
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mitchellsundt mitchellsundt

Labels
bug good first issue Good for newcomers! Experienced ODK devs, only take these if they need to be fixed quickly. =) help wanted Issues that are well-specified and don't require too much context.
Projects
None yet
Milestone
April 2017
Development

No branches or pull requests
5 participants
@yanokwa @lognaturel @mitchellsundt @greg-mogavero @getodk-bot